# Database issues with droneCI \>1.0.0 **URL:** \ **Category:** Drone Support\ **Created:** [April 3, 2019, 7:21pm UTC](https://drone.discourse.group/t/database-issues-with-droneci-1-0-0/10826 "2019-04-03T19:21:54Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![sebastianwahn](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/sebastianwahn/32/4974_2.png) [@sebastianwahn](https://drone.discourse.group/u/sebastianwahn)\ **Post date:** [April 3, 2019, 7:21pm UTC](https://drone.discourse.group/t/database-issues-with-droneci-1-0-0/10826/1 "2019-04-03T19:21:54Z")
Im currently trying to set up drone with the helm chart version 2.0.0-rc.7 and drone version 1.0.0-rc.5 I face different issues with the DB when setting up the connection to AWS RDS / MariaDB. DB charset: When I set the charset of the database to “utf8” with coallation “utf8\_general\_ci” or “utf8mb4” with coallation “utf8mb4\_general\_ci” then the error: " Error: Specified key was too long; max key length is 1000 bytes" pops up and drone does not start. This can be fixed by using the charset “latin1”, but I guess a “utf8” support would be quite nice. Database Triggers: After fixing the above error by setting the charset to “latin1”, drone complains that: " You do not have the SUPER privilege and binary logging is enabled". Which seems to be raised when database triggers are used (at least according to this: [https://techtavern.wordpress.com/2013/06/17/mysql-triggers-and-amazon-rds/](https://techtavern.wordpress.com/2013/06/17/mysql-triggers-and-amazon-rds/)). Is there any chance, that I can turn off those triggers and maintain a untriggered droneCI? ---
**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\ **Post date:** [April 3, 2019, 8:32pm UTC](https://drone.discourse.group/t/database-issues-with-droneci-1-0-0/10826/2 "2019-04-03T20:32:52Z")
I recommend testing 1.0.0 instead of 1.0.0-rc.5. I am pretty sure we changed some of the column sizes prior to the 1.0.0 final release. ---
**Author:** ![sebastianwahn](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/sebastianwahn/32/4974_2.png) [@sebastianwahn](https://drone.discourse.group/u/sebastianwahn)\ **Post date:** [April 4, 2019, 9:55am UTC](https://drone.discourse.group/t/database-issues-with-droneci-1-0-0/10826/3 "2019-04-04T09:55:46Z")
Hi, I updated now to drone 1.0.0, but I still get the errors about the triggers as described in my post: “Error 1419: You do not have the SUPER privilege and binary logging is enabled (you _might_ want to use the less safe log\_bin\_trust\_function\_creators variable)”. Is there a way to not setup triggers for drone somehow? Also when using utf8 again, the key length error still occurs: “Error 1071: Specified key was too long; max key length is 767 bytes” ---
**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\ **Post date:** [April 4, 2019, 12:56pm UTC](https://drone.discourse.group/t/database-issues-with-droneci-1-0-0/10826/4 "2019-04-04T12:56:24Z")
> Is there a way to not setup triggers for drone somehow? Sorry, triggers are required for mysql to compensate for their lack of partial indexes. They are _not required_ for sqlite or postgres. > Also when using utf8 again, the key length error still occurs I am unable to reproduce errors with `mysql:5.7` or `mysql:8`. For reference, is the docker configuration that we use in our unit testing: ```plaintext docker run \ -p 3306:3306 \ --env MYSQL_DATABASE=test \ --env MYSQL_ALLOW_EMPTY_PASSWORD=yes \ --name mysql \ --detach \ --rm \ mysql:5.7 \ --character-set-server=utf8mb4 \ --collation-server=utf8mb4_unicode_ci ``` ---
**Author:** ![sebastianwahn](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/sebastianwahn/32/4974_2.png) [@sebastianwahn](https://drone.discourse.group/u/sebastianwahn)\ **Post date:** [April 5, 2019, 8:38am UTC](https://drone.discourse.group/t/database-issues-with-droneci-1-0-0/10826/5 "2019-04-05T08:38:28Z")
Thanks @bradrydzewski for the info. I noticed I use AWS RDS MariaDB in version 10.1 which seems to be compatible to MySQL version 5.6. Maybe this is the issue here for the charset/coallation problems. Although, I think the simplest for me would be to use SQLite or Postgres now, since I don’t like the fact to enable triggers for my whole RDS instance. Thanks again for your support! ---
**Author:** ![Veitor](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/veitor/32/5077_2.png) [@Veitor](https://drone.discourse.group/u/Veitor)\ **Post date:** [April 24, 2019, 2:56pm UTC](https://drone.discourse.group/t/database-issues-with-droneci-1-0-0/10826/6 "2019-04-24T14:56:47Z")
Is the official not going to deal with mysql5.6 compatibility issues? I have encountered this problem in the 0.x version, and now this problem exists on the 1.x version. ---
**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\ **Post date:** [April 24, 2019, 2:58pm UTC](https://drone.discourse.group/t/database-issues-with-droneci-1-0-0/10826/7 "2019-04-24T14:58:25Z")
Drone officially supports mysql 5.7 and higher. ---
**Author:** ![Luis](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/luis/32/4291_2.png) [@Luis](https://drone.discourse.group/u/Luis)\ **Post date:** [April 30, 2019, 7:45am UTC](https://drone.discourse.group/t/database-issues-with-droneci-1-0-0/10826/8 "2019-04-30T07:45:05Z")
i had the same issue with drone 1.1.0 + mysql5.7, but i am using mysql from a cloud provider. I change the innodb\_large\_prefix = 1, and it works fine. hope it help. reference: - [https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes](https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes) - [https://dev.mysql.com/doc/refman/5.7/en/create-index.html](https://dev.mysql.com/doc/refman/5.7/en/create-index.html)