On Jul 6, 4:31 am, "David Crawshaw" <[EMAIL PROTECTED]> wrote: > From a practical standpoint I agree, and I will definitely keep the > Connection thread-safe. But I'm not going to make Statement > thread-safe.
Connection pooling in multi-threaded apps is common, and PreparedStatement pooling is sometimes seen. It certainly makes sense to keep Connection thread-safe. It might be good to do the same for PreparedStatement. There seems to be little reason to make Statement, ResultSet, etc. thread-safe because pooling them for use by multiple threads is an unlikely design. FYI - the JDBC 3 spec mentions Connection pooling and PreparedStatement pooling, but I can find no other reference (or inference) of thread-safety in any of the JDBC specs. -tom- --~--~---------~--~----~------------~-------~--~----~ Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
