#756 Bug ? Mariadb - Column Type DateTime - Forced to Be - On Update / Current TimeStamp

[MarcoCzen]

Hi,

Re: Bug ? Mariadb - Column Type DateTime - Forced to Be - On Update / Current TimeStamp

I have noticed this issue/bug in the latest version of adminer ( i switched from phpmyadmin to adminer from last year ) and the versions prior too.

For column 'datetime',;

In phpmyadmin -> u have options None, As Defined, Null, Current TimeStamp
In Adminer -> u have options On Update, Current TimeStamp

Say we create a datetime column as below;

user_date_added datetime NOT NULL DEFAULT '2000-12-30 11:11:11' COMMENT 'Date User Added. YYYY-MM-DD HH:MM:SS '

Even if this table/column were created manually(not via adminer) , when we use adminer to alter table ( to change other columns), columns with datetime type will not honor the settings they were created with but show a options On Update, Current TimeStamp.

In my humbleopinion , it should puckup the the setting the columns was created with or leave it empty to avoid changes to the column type.

[Jakub Vrána]

(ON UPDATE) is just the title for the option list. The default value is preserved.