Ed Leafe wrote: > On Feb 13, 2007, at 5:55 PM, Uwe Grauer wrote: > >> Thinking about this some more, i would like to have the ability to get >> connections by name out of a pool of connections. >> With using only one connection in an app i'm not able to detach >> another >> functionality. Both are running in the same connection. > > I don't understand the issue here. What do you mean by "detach > another functionality"? >
Running in different transactions. >> If i use a connection for every form, i can't run the same form twice. > > Why not? > >> So i think it would be useful to extend the current funcionality >> for the >> use of a connection pool. >> I'm thinking of something like: >> getConnectionByName(self, connName, newcon=False) >> to get either the one and only connection by this name, or get a >> new or >> open connection from a pool. >> To release the connection from the pool we could have: >> releaseConnectionFromPool(self, con) > > Dabo is designed for the cases that will handle the vast majority of > situations, but still allow the occasional esoteric usage such as you > seem to be asking for. > Running different functionality or just forms in different transactions isn't esoteric usage at all! > If you want manual connections, you can certainly do it yourself: > > ci = dabo.db.dConnectInfo(DbType="Firebird", Host=...) > conn = dabo.db.dConnection(ci) > > ...and there's your connection. Ok, if you don't think it's useful inside of dabo, i do it anyway because i think its not generic enough to get a connection by name only. Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
