noble timber
Yesterday I discovered that my MariaDB is NULLing out a bunch of critical data, see states below. Worst part I dont get entity ID's and will likely end up losing all the historical data because of the NULLS. Maybe I am a NULL too - or close to it. Worked myself through installing HA and several others on Ubuntu with Docker and was kinda of happy that I got that far. But now I am, besides frustrated that I did not catch this earlier, and baffled because I seem to be stuck despite using a good amount of time mixed with some LLM's trying to work through this and get it solved. Turns out I have a bunch of characters with 0 length Char(0) in the scheme that just don't allow anything else in that field besides a NULL. Long story short - I cant get it to create the correct data types. No matter what I do deleting the complete DB, going to older Versions of MariaDB, trying to produce own container with an older SQLAlchemy definition (leads to other issues) even going to give up MariaDB and switching to PostGRE 16 doesn't seem to solve the issue - there I have Char(1) definitions that appear to be too short as well. And - it always comes up again even when starting from scratch with a whole new DB.
I have the output for SHOW CREATE TABLE states for MariaDB as well as PostGRE but too much for this post.
The LLMs are saying its because of HA going to SQLAlchemy 2.x which leads to incompatibilities with many external DB's and many users are affected, however - I couldnt really find any other post addressing this issue...
--> Does anybody else run into these issues too - and maybe knows how to fix?
First post - wasn't sure which category it would fit best, hope it can be moved to the correct by somebody that doesnt have that many NULLs in his DB. 🙂