some may-be-stupid answers: - see the number of lines per file - split it into app-field-related parts, not SA-arhitectural parts - hell, do as it is easier - start as one file, once u hit some limit of your nerve(r)s, split.. but do keep one single file as main entrance point
On Thursday 20 December 2007 09:37:26 Morgan wrote: > Hi Guys, > > This may be a stupid question so flame away I don't care, but I > have been wondering. Is there a better way to layout your SQL > alchemy files that my random method? Does anyone have a convention > that works well for them. > > I'm only asking this because I cannot decide how I want to lay out > the SQLAlchemy component of my application. > > I'm thinking of putting it all in files like engines.py, > mapping.py, metadata.py etc or should I just shove this all in one > file. > > Let me know if I have had too much coffee or not. > Morgan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
