You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, if I have a DATETIME column with a default value of CURRENT_TIMESTAMP, and I do not specify a value for this column when performing an INSERT with handlersocket - I get "0000-00-00 00:00:00". Same id true for a column of type TIMESTAMP which has "DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP". On insert, if I don't specify a value by hand, it gets created with "0000-00-00 00:00:00". In case I update a row and do not specify a value for the timestamp column, it remains the same as before update. Thus, I have to track all this stuff on the app level. This is not critical but annoying.
The text was updated successfully, but these errors were encountered:
At the moment, if I have a DATETIME column with a default value of CURRENT_TIMESTAMP, and I do not specify a value for this column when performing an INSERT with handlersocket - I get "0000-00-00 00:00:00". Same id true for a column of type TIMESTAMP which has "DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP". On insert, if I don't specify a value by hand, it gets created with "0000-00-00 00:00:00". In case I update a row and do not specify a value for the timestamp column, it remains the same as before update. Thus, I have to track all this stuff on the app level. This is not critical but annoying.
The text was updated successfully, but these errors were encountered: