Strapi Release: 3.0.0-alpha.13.0.1

TL;DR

Strapi v3.0.0-alpha.13.0.1 addresses two critical database-related bugs: fixing morphological relation deletions in Bookshelf and upgrading MySQL text fields to longtext to prevent data truncation. These fixes ensure proper data handling and storage integrity for Strapi applications.

Highlight of the Release

• Fixed deletion of morphological relations in Bookshelf ORM
• Changed MySQL text fields to longtext to prevent data truncation
• Improved database compatibility and reliability

Migration Guide

MySQL Text to Longtext Migration

If you're using MySQL as your database, this update will change the field type from text to longtext for text fields. This change is backward compatible and shouldn't require manual intervention for most users.

However, if you have custom SQL queries or database interactions that specifically rely on the text field type, you may need to update those to work with longtext fields.

No specific migration steps are required for the morphological relation deletion fix.

Upgrade Recommendations

This patch release (v3.0.0-alpha.13.0.1) is recommended for all Strapi users running v3.0.0-alpha.13, especially those:

1. Using MySQL as their database backend
2. Working with morphological relations in their content types

The upgrade should be straightforward with minimal risk, as it only contains bug fixes without introducing breaking changes. Users should follow the standard Strapi upgrade process:

npm install [email protected]

or

yarn upgrade [email protected]

Bug Fixes

Fixed Morphological Relation Deletion in Bookshelf

This release fixes an issue with deleting morphological relations when using the Bookshelf ORM. Previously, attempting to delete these relations could fail or leave orphaned data in the database, causing potential data integrity issues. The fix ensures that morphological relations are properly deleted when requested.

Changed MySQL Text Fields to Longtext

Fixed an issue where MySQL text fields had limited storage capacity (65,535 bytes), which could lead to data truncation for larger content entries. By changing the field type from text to longtext, Strapi now supports storing much larger text content (up to 4GB) in MySQL databases, preventing unexpected data loss when saving large content items.

New Features

No new features were introduced in this patch release. This is a bug fix release focused on database-related issues.

Security Updates

No specific security fixes were included in this release.

Performance Improvements

While not explicitly focused on performance, the change from MySQL text to longtext field types removes limitations on text storage, which can improve application reliability when handling large content entries. This prevents potential performance issues that might occur when the system attempts to handle truncated data.

Impact Summary

This patch release addresses two important database-related issues that could affect data integrity in Strapi applications.

The fix for morphological relation deletion ensures that content relationships are properly maintained when deleting content, preventing orphaned data and potential inconsistencies in your content structure.

The change from MySQL text to longtext field types is particularly significant for users with content-heavy applications. MySQL's text type has a limitation of 65,535 bytes, which can be easily exceeded with rich text content, especially when including embedded media or complex formatting. By upgrading to longtext (which supports up to 4GB), Strapi ensures that content isn't unexpectedly truncated, providing a more reliable content management experience.

Both fixes contribute to a more stable and reliable Strapi experience, particularly for production environments where data integrity is critical.

Full Release Notes