Upgrading from 2023.1.7 to 2023.2.0 or .3 gives date problems in MariaDB

Installation
1

HA and MariaDB ver 10.11.1 with small working (hass) database.

Everything works great before upgrading to 2023.2.0 to 3.

The upgrade converts the database from last_updated (DATETIME) to last_updated_ts (DOUBLE) and sets last_updated to NULL. MariaDB cannot handle DOUBLE as DATETIME.

Any tips on what’s going wrong?

2

I run a script to calculate daily min, max and avg on temperature sensors. I used to have to convert last_updated to a date, adjusting for Time Zone as the last_updated was stored as GMT.
e.g.

date(CONVERT_TZ(last_updated,'GMT','Australia/Melbourne'))

last_updated_ts is now adjusted for local time zone. So now I use

date(from_unixtime(last_updated_ts))

and that has fixed my issue. Hope that helps.