The principal use for AutoConnectEngine is to support the TurboGears PackageEngine which looks in a config file (which is loaded at server startup time) to determine the dburi.

I honestly wasn't aware that create_engine worked that way, so really AutoConnectEngine could be called JustInTimeConnectEngine or something.

On 14 Mar, 2006, at 5:55 pm, Michael Bayer wrote:

on the subject of sqlalchemy.ext.proxy.AutoConnectEngine, can someone explain to me what the point of it is ?  Keeping in mind that when you make a regular SQLEngine with create_engine(), the underlying connection pool doesnt connect to the database until the connection() method on the engine is called.

--
Jeff Watkins

"Advertising directed at children is inherently deceptive and exploits children under eight years of age."
-- American Academy of Pediatrics


Reply via email to