I have a package which implements users, groups, and access control using SQLAlchemy. On top of that I'm writing applications as separate packages. These will make foreign keys into the tables of the user management package. At the moment I use separate metadata for each package, and the foreign keys are just integers. This is unfortunate due to the lack of foreign key constraints to ensure consistency of the data, and also inconvenient when using ORM.
I'd like to add the foreign key constraints. As far as I can tell, requires sharing metadata across packages. This means that create_all and drop_all no longer acts locally on the package, but their use can be avoided. Are there other consequences? Are there ways to allow cross-package foreign keys while keeping metadata separate? What is the common practice and recommendations for inter-package table dependencies? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
