https://bugs.documentfoundation.org/show_bug.cgi?id=119135
Robert Großkopf <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #18 from Robert Großkopf <[email protected]> --- tested this again. The following behavior appears only with the direct connector of LO: Open a table for editing, not for input date. Create a new field as timestamp. Save the table. The fieldtype won't be shown any more as timestamp, will be shown as datetime. Field properties for the new field will be NOT NULL. Open the same database with JDBC-connection. You could see the field is a timestamp field. And now: Open the database in phpMyAdmin. The new timestamp-field has been created as NOT NULL DEFAULT CURRENT_TIMESTAMP() ON UPDATE CURRENT_TIMESTAMP(). It will be possible to create such a field for a table, which has already been filled with content in some rows. The timestamp will be automatically set to the timestamp this timestamp-field has been created. So: There is no TIMESTAMP field modified to DATETIME. It is only shown as "DATETIME" in table editor with direct connection. Please test again. -- You are receiving this mail because: You are the assignee for the bug.
