Possible minor bug in DB definition

Hi,

Where has this database dump come from (how was it created and what version of SQL)?

In the AIOS codebase that table has not long been added and the SQL for the created field doesn’t look like that.

The SQL in the codebases is:

created datetime NOT NULL DEFAULT '1000-10-10 10:00:00'

All the other tables created by the plugin also use the same options for time based fields, do they also cause errors?

If not what have they been exported as?

Best Wishes,

Ashley

The dumps were generated by the Plesk Export Dump utility, and returned the exact same error on every single migration.

The table structure on phpmyadmin looks like this: https://ibb.co/T0BM5Kp

On the rest of the tables, the datetime fields default value is set to 1000-10-10 10:00:00 and don’t cause errors. It’s only the debug_log table that does that.

Thats very odd how it’s ended up with that default when the others have the correct one.

If you drop that table and then deactivate and reactivate the plugin the table will get recreated, does it then still have the wrong default?

Best Wishes,

Ashley

Nope, it turns to

1000-10-10 10:00:00

That’s weird. Does that make sense to you?

@beerallica

Yes it will have default ‘1000-10-10 10:00:00’ and it makes sense.

Here what you have used plesk utility it did not exported the correct created field definiation it is an issue.

Also it seems try import in mysql 5.5 which is creating issue for current_timestap()

created` datetime NOT NULL DEFAULT '1000-10-10 10:00:00',

https://www.loom.com/i/9cb9fa8fd11846f9870906c2455ee0fb

It is good to have datetime type used with default ‘1000-10-10 10:00:00’ instead changing type from datetime to timestamp ( which might be an issue in terms of functionality with other tables showing datetime) as the debug_log is the first table it returned error. there it will be issue for all tables up to I think.

Solution) change default value to ‘1000-10-10 10:00:00’

Regards