268425b5e3
* Handle statistics columns being unmigrated from previous downgrades If the user downgraded HA from 2023.3.x to an older version without restoring the database and they upgrade again with the same database they will have unmigrated statistics columns since we only migrate them once. As its expensive to check, we do not want to check every time at startup, so we will only do this one more time since the risk that someone will downgrade to an older version is very low at this point. * add guard to sqlite to prevent re-migrate * test * move test to insert with old schema * use helper * normalize timestamps * remove * add check * add fallback migration * add fallback migration * commit * remove useless logging * remove useless logging * do the other columns at the same time * coverage * dry * comment * Update tests/components/recorder/test_migration_from_schema_32.py |
||
|---|---|---|
| .. | ||
| auto_repairs | ||
| history | ||
| models | ||
| system_health | ||
| table_managers | ||
| __init__.py | ||
| backup.py | ||
| const.py | ||
| core.py | ||
| db_schema.py | ||
| entity_registry.py | ||
| executor.py | ||
| filters.py | ||
| manifest.json | ||
| migration.py | ||
| pool.py | ||
| purge.py | ||
| queries.py | ||
| repack.py | ||
| services.py | ||
| services.yaml | ||
| statistics.py | ||
| strings.json | ||
| tasks.py | ||
| util.py | ||
| websocket_api.py | ||