Gallemarmiksoft,надеялся что всё таки возможно,раз существуют такие продукты как RubyRep.Ну так документацию читать никто не отменял.
http://www.rubyrep.org/coordinating_with_application_specific_triggers.html MySQL Limitiations
MySQL only supports one after trigger per table. Meaning if you already need an application specific after trigger for a table, you cannot replicate it with rubyrep.
MySQL also only supports one before trigger per table. By default rubyrep uses the before trigger to simulate adjustable sequences. Meaning if you already need an application specific before trigger for a table, you have to
disable the :adjust_sequences option for that table
ensure on your own that no duplicate key problems arise for the table
