triggers for copying

[ghazel]

table_migrator currently relies on updated_at/created_at, indexes on those, and avoiding things like DELETE during a migration. These problems could be solved by switching to a AFTER_{INSERT/UPDATE/DELETE} trigger-based copy mechanism.

Has this been considered? It's a bit more complicated, but I believe it's a better way to go about it.

There's a thorough explanation here: http://www.facebook.com/note.php?note_id=430801045932

[freels]

I'm aware of that blog post, though I wrote this a year or so before. I'd like to make this use triggers at some point, but I haven't had the time.