In a Google Cloud SQL 2nd generation instance, I cannot find any way to disable the peculiar MySQL treatment of timestamp fields. These legacy peculiarities are being deprecated in MySQL, and a warning is logged upon startup of the instance:
-- [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details)."
However, there does not seem to be any flag in Cloud SQL to cause this flag to be passed. Trying to change the setting at the individual session level with SET SESSION does not work either, because changing that session variable requires SUPER privileges and Cloud SQL does not support those either. Is there no way to disable the deprecated semantics of timestamp fields in Cloud SQL ?
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/b236acf3-f4f9-4759-9376-50f0202838e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment