Copy table kills TIMESTAMP attribute

[patrickq]

To reproduce, simply create any table with a TIMESTAMP column, create one row, then copy that table (structure and contents) to a new table.

Now add a new row to the new table – the TIMESTAMP column should reflect the time when that new row was addedd. Instead, the time value is all zeros, and not the time of the last update to the row, as it should be.

The new table's TIMESTAMP column doesn't act like a TIMESTAMP column any longer …

If you do click on the table under WebYog, you will see that the timestamp column has a default of 0, instead of CURRENT_TIMESTAMP. Deleting that default via “Alter Table” fixes the problem.

It seems the fix should be for copy table not to set a default value for TIMESTAMP columns.

[Ritesh]

Thanks for the report. I have forwarded the issue to my development team and I will revert back soon.

[Ritesh]

We tried to reproduce the problem out here but everything seems to be working fine.

We tried on SQLyog Enterprise 4.0 with MySQL v4.1.7.

Can you tell me your SQLyog and MySQL server versions?

[Author]

Posts