<div dir="ltr"><br><div>Some History:</div>In `MariaDB 10.1.2` a new temporal format was introduced from `MySQL 5.6`<br>that alters how the `TIME`, `DATETIME` and `TIMESTAMP` columns operate at <br>lower levels. <br>These changes allow these temporal data types to have fractional parts and<br>negative values. <br>You can disable this feature using the mysql56_temporal_format system variable.<br><br>```<br><span style="font-family:monospace">MariaDB [(none)]> SHOW VARIABLES LIKE 'mysql56_temporal_format';<br>+-------------------------+-------+<br>| Variable_name           | Value |<br>+-------------------------+-------+<br>| mysql56_temporal_format | ON    |<br>+-------------------------+-------+</span><br><br>```<br><br>Starting from `MariaDB 10.5.1` columns with old temporal formats are marked with a<br>`/* mariadb-5.3 */` comment in the output of `SHOW CREATE TABLE`, `SHOW COLUMNS`,<br>`DESCRIBE` statements, as well as in the `COLUMN_TYPE` column of the <br>`INFORMATION_SCHEMA.COLUMNS` Table.<br><br>Details on <a href="https://mariadb.com/kb/en/datetime/#internal-format">https://mariadb.com/kb/en/datetime/#internal-format</a><br><br>This change causes the MythTV python bindings to fail, because the<br>`datetime,` `timestamp` and `time` types are not correctly detected and not <br>converted from UTC to the local time.<br><br>See github issue #384  <a href="https://github.com/MythTV/mythtv/issues/384">https://github.com/MythTV/mythtv/issues/384</a><br><br>Please check your installation by<br>```<br><span style="font-family:monospace">MariaDB [mythconverg]> describe program;<br><br>+------------+----------------------------+------+-----+---------------------+-------+<br>| Field      | Type                       | Null | Key | Default             | Extra |<br>+------------+----------------------------+------+-----+---------------------+-------+<br>|   .....    |                            |      |     |                     |       |<br>+------------+----------------------------+------+-----+---------------------+-------+<br>| starttime  | datetime /* mariadb-5.3 */ | NO   | PRI | 0000-00-00 00:00:00 |       |<br>+------------+----------------------------+------+-----+---------------------+-------+<br>|   .....    |                            |      |     |                     |       |<br>+------------+----------------------------+------+-----+---------------------+-------+</span><br>```<br><br>If so, could you please test the patch v2 attached to #384 and report back?<br><br>I am curious if this also happens, if I do a fresh install and apply a<br>database backup made by MariaDB 10.3 afterwards. <br>I will test this over the weekend.<br><br>Thank you,<br>Roland </div>