Ouch. Very special, imo... this means the connection is re-negotiated for
each statement? Sounds strange. Maybe the client connection is 'virtual' or
'by proxy', so that multiple users actually share the same connection at the
same time?
If you want to think of it that way, yes -- there is *one* user: Tomcat. It "proxies", if you like, all requests from *end users* through its connection pool to the MySQL server.
> Sounds like it by your description. When you say user #1 and user
#2, you really mean session #1 and session #2, right? (In this context, one click from a user is one session, usually containing multiple queries against the mysql server.)
I think we have a terminology disconnect :-) To me a session is an HTTP session, managed by the servlet container. The point of creating the temp table was to place it in session scope, to save customer selections for the life of that HTTP session...
But regardless, in that case I was referring to the requests of discrete end users -- make that "end user 1" , "end user 2".
How does transactions work in such an environment? Can they be used at all?
Dunno. Haven't had a need.
I don't know dbcp, but being under the wings of Jakarta I would expect a certain level of quality... I don't have any experience with Tomcat either,
Well, that could explain why this seems unfamiliar :-)
Do the Web application environments you've used handle connection pooling differently, then?
-- Hassan Schroeder ----------------------------- [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com
dream. code.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
