In my opinion it's best to keep the 'application model' all in one place as it shows you at a glance the relationships within the app.
On Sun, Oct 31, 2010 at 7:08 PM, Daniel Meier <herr.schn...@gmail.com> wrote: > Hi list > > I have tried the examples in the ORM tutorial and I'm wondering how I > can separate different models into own modules. > > Let's say I have a "BankAccount" model and a "BankCustomer" model. My > idea would be to create two modules, bankaccount.py and > bankcustomer.py, and a database handler that imports the necessary > stuff from that modules. > > This is what I came up with: http://pastie.org/1262474 > > Actually, it doesn't work because the database was not yet initiated > (metadata.create_all). Where should I put that? Or is my idea of > splitting up a bad one? > > Daniel > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@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. > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@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.
