Magento 1.13 and MySQL Triggers

I know “no more consulting” was a great business move for Varient/Magento Inc./etc., but the folks building Magento’s core are slowly loosing touch with the day-to-day needs of working developers.

I’m glad there’s folks like Robert willing to suffer the slings and arrows of unfinished features and share solutions with the rest of us. Here’s his entire tweet storm on the problems with triggers in PHP web applications.

@benmarks @aligent Multipart tweet, part 1: Magento will create the new update triggers using the MySQL usr set for the DB you frst install

— magento tutorials (@magebase) May 22, 2013

@benmarks @aligent Part 2: Then when you replicate your dev environment elsewhere, triggers are imported using that original user as the…

— magento tutorials (@magebase) May 22, 2013

@benmarks @aligent Part 3: …trigger definer. If that user doesn’t exist in the target DB, you have problems as triggers don’t execute…

— magento tutorials (@magebase) May 22, 2013

@benmarks @aligent part 4: seems to us as a big oversight on the Magento devs. At least this should be documented.

— magento tutorials (@magebase) May 22, 2013