Update SQL Storage Models for MySQL and MariaDB Support #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
To ensure seamless compatibility with MySQL and MariaDB databases, we need to update column data types in our SQL storage models. The main objective of this update is to address a specific requirement in MySQL and MariaDB that requires a length specification for VARCHAR columns.
Exception Without the Update
Without these modifications, attempting to use
sqlalchemy.String
typed columns in MariaDB (or MySQL) results in the following error:Changes Made
Modified Files
sqlalchemy.String
tosqlalchemy.TEXT
to maintain the datatype while ensuring compatibility with MySQL and MariaDB dialects.