simulate sequence on mysql in preparation for move to oracle
The 'gotcha' is that in nearly every case you really don't want to take the performance and maintenance hit for triggers just to hide the pk insert.  

You really should write the queries to insert sequence.nextval with the INSERT.  Do it during the migration before you regret it a few years from now.