Migrate? I'm afraid not. It only uses a version number on the database to keep things synced, and expects that this version number is incremented every time the schema is changed. (Migrate manages the version number.) There's no comparison of tables/triggers/functions to ensure that's correct.
On 10/27/06, Jonathan Ellis <[EMAIL PROTECTED]> wrote: > > I have two databases that are supposed to be kept in sync. I suspect > that because of human error they might not be. Can Migrations help > compare tables, triggers, functions and tell me what doesn't match? > > > -- > Jonathan Ellis > http://spyced.blogspot.com > > > > -- - Evan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~----------~----~----~----~------~----~------~--~---
