[sqlalchemy] Re: The Minimalists' strategy for SQLAlchemy.

2011-05-01 Thread Kuze
You can reflect once, then cache the metadata (e.g. pickle it) GHZ, At the moment not sure I'd like to deal with managing a cache in the DAL. But I'll keep it on the utility belt as a possible option. Could come in handy at least for local development. Thanks for the reply. -- You received

[sqlalchemy] Re: The Minimalists' strategy for SQLAlchemy.

2011-05-01 Thread Kuze
Michael, Thanks for the executive summary, exactly the info I was curious about. CreateTable functionality looks promising. -- 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

[sqlalchemy] Re: The Minimalists' strategy for SQLAlchemy.

2011-05-01 Thread Kuze
David, Well said. Thanks for taking the time to give a high level view of your workflow. On the path to finding a somewhat even ground myself, I'll be taking what you've outlined into consideration while doing a few tests with reflection. -- You received this message because you are subscribed

[sqlalchemy] Re: The Minimalists' strategy for SQLAlchemy.

2011-04-30 Thread GHZ
You can reflect once, then cache the metadata (e.g. pickle it) then I think you can use autoload with usexisting On Apr 30, 12:13 am, Kuze kuze.to...@gmail.com wrote: I'm aware SQLAlchemy provides a comprehensive package for creating database objects (tables, indexes, etc.) with a simple

[sqlalchemy] Re: The Minimalists' strategy for SQLAlchemy.

2011-04-30 Thread David Bolen
Kuze kuze.to...@gmail.com writes: I'm also aware of `reflection` capability provided. However, it'd be hitting the database with a query to grab the necessary data points for generating the schema. For production, hitting the db when using reflection does not sound compelling. With my