I have successfully set up Eramba on AWS, but using RDS means that I have to follow AWS’ guidelines for MySQL/MariaDB parameters. This is fine as you can set most of them properly, but sql_mode is an issue because a blank entry is not accepted here.
Does anyone else have experience with this? What settings did you end up using? Mine currently looks like this, but I don’t want to enter prod with potential issues in the SQL configuration. The settings here were configured by me, originally it seemed to be in standard strict mode.
You changed the RDS parameter in this case? I am trying to use a shared, already configured RDS instance. And it has very different settings for sql_mode. No idea what the impact might be.
So why is this specific setting required?
I am getting errors like
triggering handler | Create eramba schema
10.0.196.95 | FAILED | 26695ms
- msg: mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1227 (42000) at line 9597: Access denied; you need (at least one of) the SUPER privilege(s) for this operation
Which is for this statement
/*!50003 CREATE*/ /*!50017 DEFINER=`eramba`@`localhost`*/ /*!50003 TRIGGER `user_fields_groups_after_insert` AFTER INSERT ON `user_fields_groups` FOR EACH ROW INSERT INTO `user_fields_objects`
model = NEW.model,
foreign_key = NEW.foreign_key,
field = NEW.field,
object_id = NEW.group_id,
object_key = concat('Group-', NEW.group_id),
object_model = 'Group',
created = NEW.created,
modified = NEW.modified */;;
Isn’t this commented out?
On my RDS instance it does have NO_ENGINE_SUBSTITUTION set, but it also has lots of other settings: