mariadb default for current_timestamp

[zokkis]

Describe the bug
A table with a timestamp column with default of CURRENT_TIMESTAMP returns current_timestamp() in mariadb.
But in transporter.py it only checks for CURRENT_TIMESTAMP.
So for a table like

CREATE TABLE test (
time TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

The sqlite3 Table is with default 'current_timestamp()' and don't get filled with the current timestamp, but with this string.

My version is 2.4.1 and mariadb 11.6

Is this something that will be fixed or is this out of scope?

[techouse]

Hey,

Is this a MariaDB specific quirk? I have just tried the above with MySQL 9.3 and it works as expected and produces this SQLite DDL

CREATE TABLE "test" (
  "time" DATETIME NULL DEFAULT CURRENT_TIMESTAMP
);

[zokkis]

Yes I know, and this is the reason I wrote MariaDB in the title.
And maybe its out of the scope of this project to also support MariaDB, then sorry to bother you and you can close the issue.

[techouse]

Hmm, I see. MariaDB is becoming increasingly strange. Could you please provide information about the version when this started happening, as it wasn’t an issue in older versions?

[zokkis]

I only tried it on a MariaDB 11.6 Image and its my first time using this lib to migrate. So I can test it and send you the result in a few minutes

[techouse]

It might just be my ignorance, but I’ve always given MariaDB support a low priority simply because it started drifting from MySQL’s standards.

[zokkis]

I dont know anything about the state of this 2 databases, its just for my work.
But i testet the database and in version 10.1.48 its CURRENT_TIMESTAMP and at version 10.2 itd current_timestamp()

[techouse]

Would you mind checking out PR #100 and testing it on your database?