Well thank you guys for your help.
I found the way how Django (if you know it) separates the modules
great. But I can also live with a single module containing all models.
I played some time with sqlalchemy now, and I created two classes in
my db.py file (see http://pastie.org/1264141). In the
Thanks Michael
I must admit that I completely misunderstood the session. It was clear
to me that everything done until session.commit() is in a transaction,
but I somehow had no idea how to implement it and ended up creating
those micro-sessions.. Still not sure where to put the business
logic.
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
