Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Hello,
we provisioned a MySQL instance and intend to connect a third party application to it. Namely, the Directus Headless CMS.
During debugging on why directus is not compatible with the managed MySQL instance, we found that the sql_mode is set to something that Directus can not work with.
To be specific: The managed MySQL instance on DigitalOcean has the sql_mode set to
REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,ONLY_FULL_GROUP_BY,ANSI,STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION
Our local testing database (which Directus works with without problems) it is set to
ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
We know that the ANSI_QUOTES option is conflicting, since Directus produces SQL statements that use double quotes for strings, which is what this option prevents.
We are not sure if other options cause any problems.
As per documentation it is not possible for us to get root access, which we would need to change the sql_mode setting.
Is it possible for DigitalOcean staff to change this setting for us?
hbarnard
keneucker
keneucker
rich
santoshpatil
Aspiresoftserv
Yakin
Thejaswini-Rao-U
775c69c916d345a7a367d867078ccb
mayricoak
ndam
bc2f52583874402a988f587c00195d