On Tuesday 13 February 2007 16:00, Uwe Grauer wrote: > johnf wrote: > > On Tuesday 13 February 2007 15:21, Uwe Grauer wrote: > >> Running different functionality or just forms in different transactions > >> isn't esoteric usage at all! > > > > Actually that's a good question. I believe in the VFP world and using an > > ODBC/ADO as the connection - you a connection pool. Is that true for > > all the database drivers we use with Dabo? > > The python db api does not provide pooling. > For dabo, a connection name (see dApp) is unique. > So dabo doesn't support connection pools by the same connection name. > You can mimic it by using different connection names (hard to do generic > because the names should be predefined in the cnxml file) or by > providing a dConnectInfo object for dConnection() yourself. > Psycopg (connection to Postgres) does maintain connection pooling without violating python's DB API 2.0. For each cursor created a new connection is used from the pool. I'll check into how Dabo uses the cursor. BTW a "cursor" as in cursor = conn.cursor()
-- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
