For me, using JDBC to connect to oracle is getting the driver and catch the exception if driver not found. Then I will connect using the driver.
What is more to JDBC and oracle? why make a whole book? Is there something like handling intensive user? How about handling concurrent request?
I think I need the book.
Thank you, David
Hi David This is a very valid question though of course there is more to it than just "connecting and catching exception".. After all JDBC is just an API. There are multiple reasons I chose to write this book: 1. Currently available books on JDBC on Oracle seemed (to me at least) to be more of a rehash of existing documentation. I wanted to create something that will compliment the existing JDBC and Oracle documentation. 2. I wanted to emphasize how when using Oracle, you should write your applications. 3. Another reason was to somplify the explanation that may be too complicated in the docs and may not be explained well enough in other books. 4. Most books that I saw had erroneous information or information partially correct _ strived to write a perhaps, more well researched book. 5. Wanted to bridge the gap between J2EE guys and database (at least those using Oracle) guys.. 6. Wanted to explore in the book performance enhancing techniques specific to JDBC and Oracle.
PS: Yes the book talks of concurrency concepts but in the context of Oracle (Since concurrency for the most part belongs to the database.)