> Here goes: > > 1) all model classes are defined in 1 file together with database mapping
For this particular gripe I think you're a little off-base. This is all personal preference, and the bigger your model gets, the better off you are breaking it up. Google around a bit and you'll find a few different strategies for splitting the model up into more logical chunks -- it's a fundamental feature of SQLA. All you have to do is import the relevant modules into your model/__init__.py and you're in business. And frankly, you're not married to that either -- it's just a convenience. You could import your model modules one at a time so long as you take care to set up the session and meta. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
