Thanks for that, make sense to me.
svilen wrote:
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
4 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: Conventions for crea...