As regards TRIGGERS in MySQL I am very much missing what PostgreSQL (and maybe other RDBMS as well) has: an option to [temporarily] disable TRIGGGER[S] for all or specific users - like listed in PostgreSQL docs: ( http://www.postgresql.org/docs/9.2/static/sql-altertable.html)
ALTER TABLE .. DISABLE TRIGGER [ trigger_name | ALL | USER ] ENABLE TRIGGER [ trigger_name | ALL | USER ] .. A TRIGGER may work fine with the application it was designed to be used with. But you may need to do some manual maintenance and then it is not always desirable that TRIGGERS will fire. It can actually start a chain of unwanted changes that can be very dificult to correct (unless you resort to the brutal solution of taking the database offline, dropping TRIGGERS, do the maintenance and recreate the TRIGGERS). (unrelated to the code review requested, of course). -- Peter On Mon, Feb 9, 2015 at 1:44 PM, Alexander Barkov <b...@mariadb.org> wrote: > Hi Serg, > > Please review a patch for MDEV-7286. > > Thanks. > > _______________________________________________ > Mailing list: https://launchpad.net/~maria-developers > Post to : maria-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-developers > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
