| Author |
JDBC: connection pooling
|
shanmukhan battinapati
Greenhorn
Joined: Feb 24, 2010
Posts: 8
|
|
Hi,
Can any body explain the following:
"In releases prior to JDBC 2.0 every database session requires a new connection and login even if the previous connection and login used the same table and user account. If you are using a JDBC release prior to 2.0 and want to improve performance, you can cache JDBC connections instead."
URL: http://java.sun.com/developer/onlineTraining/Programming/JDCBook/conpool.html
Thanks & Regards
Shanmukhan.B
|
 |
Joe Ess
Bartender
Joined: Oct 29, 2001
Posts: 8260
|
|
The JDBC API changed in big ways between version 1 and 2 so they require different caching strategies.
One word of warning, the book you are reading was written over 10 years ago. The JDBC API alone has gone through 2 more major revisions. The Java API has had 4 major revisions.
|
"blabbing like a narcissistic fool with a superiority complex" ~ N.A.
[How To Ask Questions On JavaRanch]
|
|
Jeanne Boyarsky
internet detective
Marshal
Joined: May 26, 2003
Posts: 26168
|
|
|
Did you know we have a JDBC forum? Moving there.
|
[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
|
|
 |
|
|
subject: JDBC: connection pooling
|
|
|
0
