You could also just use one pool per user role and look up the db user
and the role that user is in, then pull the connection from the pool
that you have for that role. If your DB doesn't support roles for
users you could create a user/role table. I think it might be
overkill to create an
Hi,
I have a question regarding connection pools and DB user rights.
When you use connection pool objects you specify an user who will be the
owner of all the Connection objects in the pool.
I guess that the most usual case is to specify an user which has the DB
permissions to execute all the DB
I do not know of any, but it is possible to create one using something
like proxool.
Larry
On 7/6/05, Tamas Szabo [EMAIL PROTECTED] wrote:
Hi,
I have a question regarding connection pools and DB user rights.
When you use connection pool objects you specify an user who will be the
owner
I guess I could use any implementation of a connection pool for a simple
implementation. I just need to use a connection pool for every user (of
course using a smaller number of connections than usually).
The connection pool object will be created only when the user logs in
(if it doesn't exist
A couple of considerations are relevant here:
* Is a single user ever going to really use more than one
connection from the pool? If not, wouldn't it be better
to create a *connection* for them, instead of a *pool*?
(Note in particular that transactions don't cross connection
boundaries,
5 matches
Mail list logo
