Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEFAULT CURRENT_TIMESTAMP, ON UPDATE CURRENT_TIMESTAMP #108

Open
crocodile2u opened this issue Feb 22, 2016 · 1 comment
Open

DEFAULT CURRENT_TIMESTAMP, ON UPDATE CURRENT_TIMESTAMP #108

crocodile2u opened this issue Feb 22, 2016 · 1 comment

Comments

@crocodile2u
Copy link

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.

@oucil
Copy link

oucil commented Sep 11, 2018

I see this is quite old, but I can confirm that this is still an issue, at least it is in Percona 5.6 with handlersocket plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants