Suha Onay wrote: > > Hi, > > I plan to use the migrate.versioning.api to manage the versions of the > tables. > But there are different repositories belonging to the modules of my > project. > Each module has its own repository but will refer to the tables of > other modules. Is it possible? > > I have 2 different repositories: say X and Y > The users table is created in repository X. > And the customers table in repository Y refers to the users table. > > When api.upgrade is called for X, the users table is created. > But then, when api.upgrade is called soon after for Y, it gives an > error saying no users table.
this is more a question for the migrate list. It sounds like you may consider your two groups of tables as two different "databases" - if Migrate offers options to set the name of the "migrate table" where the version number is stored, or some other way to store multiple version numbers in one database, that would be the way to go - each respository would track the "version" in a different row and/or table. You'd need to ask on their list if this is possible. --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
