Wait WTF MySQL implicitly inserts `CURRENT_TIMESTAMP` for `TIMESTAMP` columns by default?! And `foo TIMESTAMP DEFAULT NULL` is not valid in MySQL? WHAT THE ACTUAL FUCK?!pic.twitter.com/ulGqrw6S6B
Show this thread
-
-
This was completely moot anyway. You can't create a trigger in MySQL in a prepared statement because "this command is not supported yet". Awesome. Sorry MySQL Diesel users, you get to deal with `updated_at` yourselves.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It's because you didn't specify NULL to be allowed for the timestamp field, and by default it's incompatible type (aka Timestamp vs Option<Timestamp>).
-
So `bar TIMESTAMP NULL DEFAULT NULL` works here... That doesn't make this better though. `NULL` is the default in SQL. It is the default in MySQL for every other type. You need to explicitly state `NOT NULL`. Why on earth would this be different?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.