Wait....now that I have the db and tables for the triggers etc, what's that all about?
The tables allow me to take triggers offline and put them online in a way that emulates Oracle's capabilities. Try this:
Click on Script Explorer, choose a database, choose Triggers, choose a table.
You should get the Trigger Grid, which looks like this:
Click on the "new" icon and you should get a new trigger in the editing pane and the icons will change for THAT EVENT. Note the "On / Off" switch - all triggers start in an offline state. The under-the-hood deal is that they are kept in my table, not in the MySQL triggers tables. You can edit and create all kinds of problems and still save them when they are offline. When you click the switch to the right, I attempt to move the trigger from the offline table to an actual trigger, for that DB/Table/Event. if there's no syntax errors, it'll go online. If there are errors, it'll stay in the offline position until you fix them.
I was working on a "Best Practices" thread starter for this morning (not because I'm smart about it, but in fact because I have questions for the board myself) ... so this might be more clear then.
