Problems with microseconds and mariadb

[pyloor]

Hi,

i have a strange problem with dbForge (6.3.341) and the following definition:

DATETIME(3)

I use MariaDB 5.5. In the table edit mode I change the fieldtype to DATETIME(3) and save it. Nothing happens. If I remove the length from datetime the update is send to the server.

If i define a full table (multiple rows) and one of the types has DATETIME(3) no changes are saved and all edits are lost. I created my table now several times until I recognized that it must due to the length setting for the DATETIME type.

MariaDB is able to use microseconds since version 5.3.

Kind regards,
pyloor

[alexa]

We will fix this issue in one of the next product builds and will notify you once it's available for downloading.