HandlerSocket is a NoSQL plugin for MySQL, working as a daemon inside the mysqld process, to accept tcp connections, and execute requests from clients. HandlerSocket does not support SQL queries; instead it supports simple CRUD operations on tables.
Other
1.13k
stars
150
forks
source link
DEFAULT CURRENT_TIMESTAMP, ON UPDATE CURRENT_TIMESTAMP #108
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.
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.