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 User class, I added two functions "create" and "delete". Is it "best practice" to add such functions inside the respective classes? At least, I want the code that deals with sqlalchemy in one place. I think my example is bad because I would not be able to i.e. search a user without defining one first (as "search" would be in the User class). @Mark: Your example looks great. I'll try that. Thanks! Any suggestions/best practices? 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.
