I'm searching about how to disable triggers, and seems like it's not possible under MariaDB.
My problem is, how to manage then, when you import data. I have a database where almost all business logic is inside it with triggers and stored procs. Probably, there are records autogenerated by triggers and stored-procs that were filled later by a user, and I don't know how to manage this if I import a database dump, or importing a csv file for example.
I'm sure the problem is I'm not seeing the obvious, and there are some problem in my data model, but because I'm starting with this project, I'm in time to modify what is needed, knowing best practices to take into consideration.
My question is, there are some best-practices to take into consideration, when we want to implement the business logic of an application, inside the database?
I hope I explained correctly.
This is a little Example coming to my mind: On a deployed database, there are a record that will be created from a trigger, and later, this record, is modified by the user. When import an sqldump, because this records exists, sql dump will fail trying to inserting this existing recods.