Use LONG 8000 TEXT column instead of TEXT for MySQL/MariaDB and migrate existing databases #47026
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.
Proposed change
There are some issues reported with MySQL/MariaDB databases having SQL exceptions in the HA log like "Data too long for column".
The mentioned columns are
attributes
in thestates
table andevent_data
in theevents
table. Both columns are of type TEXT, which is pretty limited in maximum size for MySQL/MariaDB.SQLAlchemy has the ability to force a specific column type for a particular DBMS.
If we force LONGTEXT in case of MySQL/MariaDB it will be more similar to other DBMSes TEXT-like columns.
The maximum length for LONGTEXT is 2^32-1, the maximum length for the current TEXT only 2^16-1.
A migration is necessary to change the column type for existing databases.
Changes:
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: