OK, but the "user" here is the servlet container (Tomcat), *not* the human end user.
That should not make a difference, as seen from the server a client is a client.
Huh? OK, Tomcat is the client of the MySQL server; "user" or "client", same situation.
As would temporary tables, which is why I stopped using them for request-specific data :-)
Right... you got errors, I assume...? What kind of connection pooling was that, was it Tomcat?
Not errors, just the same temp table being shared across end user requests.
Related to this, does each process in the query log match to a single active connection?
Yes. _database_ connection, that is... wich is not the same as _client_ connection when connection pooling is involved. :)
OK, sorry, I'm getting more confused now. :-/
There's a connection between the client (Tomcat) and the database server (MySQL), managed by a pooling implementation (DBCP).
Is that what you're calling _database_ or _client_?
Or is that connection-pool-implementation dependent?No, the server does not know about the connection pooling, and the
connection pool implementation can not change the internal mysql "process
id" (actually connection id) without creating a new connection.
OK, I'd say that answers it: I can watch (tail -f) my query log and see *one* MySQL connection id handle requests from different users on different systems. Or am I still misinterpreting something?
-- 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]
