* Hassan Schroeder [...] > Not errors, just the same temp table being shared across end > user requests.
ok... If you did this: - create temp table - use temp table - drop temp table for each session, I would expect it to work. (atleast until a session crashes before it drops the temp table.) > >>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). That is right. The way I see it there are two "connections": one from the client to the connection pool, another from the connection pool to the database. The user connects to the pool, the pool connects to the database. This is a conseptual model of "connections", the physical TCP/IP connection is between the client and the mysql server (unless proxying or similar is involved). > Is that what you're calling _database_ or _client_? Both. :) Sorry for the confusion. > >>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? No, that sounds right. I would expect all queries from one user (=one session) coming together, then all queries from the next session and so on. This is not the case with Tomcat? -- Roger -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]