I have a quick question on what to do with the metadata object when my model definition is spread across several files. It's all in the same database, all different tables, but for my own logic, I'm defining parts in different model files. I import the classes then in the __init__ file, which is imported in the app (controllers) itself. I'd like to keep the mapping per file, though. Other than that, I'm following the 'SA 0.4 for people in hurry' by Mike. So, is that possible, and what do I do with the metdata object? I would guess that only one call to MetaData() should be enough, or does it result in the same object anyway? If it's only one call, how do I get it into the other files?
As an small additional complication, some classes and tables are imported from one model file into another, for mapping relations. I'm now stuck at the point of creating the tables (using 'paster setup- app'), which complains about a non-existant table from which it needs a foreign key (table is defined in a different file, but imported for the relation. My initial guess is, that this is where the metadata object comes into play). Perhaps this is more an SA question, but since I'm using it in a Pylons context, I figure I'd ask here first. Tia, Evert --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
