Skip to main content

JDBC FAQ part3

4: What is JDBC and What are the steps to write a JDBC application?
      
The process of interacting with the database from a java application is called as JDBC(Java Database Connectivity)
To interact with the database from a java application we will use the following five   steps.
  1. load and register the driver.
  2. Establish a connection between java application and the database.
  3. prepare either statement object or PreparedStatement object or CallebleStatement object as per the application requirements.
  4. write and execute the SQL queries.
  5. terminate the connection which we have established.
5:  How to load a JDBC driver? 
    • In general sun Microsystems  has provided Driver interface for this all the database vendors has provided their own implementation.
    • If we want to use the database vendor provided Driver implementation to our JDBC application, first we need to make the availability of the respective Driver’s   .class file to JVM, for this, we need to set classpath environment variable to the location where we have the driver implementation.
    • Sun Microsystems is also provided an implementation to the Driver interface in the form of JdbcOdbcDriver class as part of the java software.
    • If we want to use JdbcOdbcDriver in our JDBC applications no need to set classpath environment variable. Why because it was already available in the java software’s pre-defined library.
    • JdbcOdbcDriver internally depends on the Microsoft product Odbc driver. If we want to use the JdbcOdbcDriver in our JDBC applications first we must configure Odbc driver, for this, we will use the following path.
Start/ conrlol panel / performance and maintenance / administrative tools / data source(Odbc)/ user dsn / click on Add / select microsofr Odbc for oracle / finish / provide data source name only / click on ok / ok.
  • To load the driver’s class bytecode to the memory we will use the following method.
Public void forName(String class name)
Eg:    Class.forName(“sun.jdbc.odbc.JdbcOdbcDriver”);
      Where forName() is a static method, which can be used to load the respective driver class bytecode to the memory.
  • Each and every driver class has already a static block at the time of loading the respective driver class bytecode to the memory automatically the available static block could be executed, by this  DriverMadoeer.registerDriver(….) method will be executed as part of the static block.
  • By the execution of the registerDriver(….) method automatically the specified driver will be registered to the JDBC application.
  • If you want to design any JDBC application, we need to use some pre-defined library, which was provided by the JDBC API in the form of java.sql package, that’s why we need to import the java.sql package in our JDBC application.
Note:-   The best alternative for Class.forName(..) is
 DriverMadoere.registerDriver(new sun.jdbc.odbc.JdbcOdbcDriver());
  To register the driver.


Comments

Popular posts from this blog

Java Server page tutorial part 3: JSP Life Cycle

JSP Life Cycle: A JSP life cycle can be defined as the entire process from its creation till the destruction which is similar to a servlet life cycle with an additional step which is required to compile a JSP into servlet. Following are the steps followed by a JSP Container: ◦ Compilation  ◦ Parsing the JSP.  ◦ Turning the JSP into a servlet.  ◦ Compiling  the servlet.  ◦ Initialization ◦ Execution ◦ Cleanup Architecture: 1.       JSP Compilation: When a browser asks for a JSP, the JSP engine first checks to see whether it needs to compile the page.  If the page has never been compiled, or if the JSP has been modified since it was last compiled, the JSP engine compiles the page. The compilation process involves three steps: ◦ Parsing the JSP. ◦ Turning the JSP into a servlet.  ◦ Compiling the servlet.  2.       JSP Initialization: When a container loads a JSP it invokes the jspInit() method before servicing any requests.  If you need to perform

OPERATION MANUAL FOR RS232 TO RS422/RS485 VICE-VERSA

INTRODUCTION: Milestone model LD-15U is a RS232,  to RS422/RS485 converter is designed for high-speed data transmission between computer system and or peripherals over Iong distance under high noise conditions. They provide dual line interface per signal. APPLICATIONS: Application for these converters can be for factory automation, Programmable logic controllers,, attendance recording systems, Barcode Readers, remote data transmission, remote terminals, EPABX etc. SPECIFICATIONS: Input: RS232-T×D, R×D, DSR (for control), GND (D9 Female connector) Output: RS422/RS485-Tx+, Tx-, Rx+. Rx-(D9 Male Connector). Each signal is protected by spike suppressor, fuse and has opto-isolation. Selection Switch: 1. Rear side has 2-way'SELECT' switch for selecting 2-Wire or 4-Wire mode in RS422/RS485 application. 2. (Optional) Rear side has 3-way'SELECT' switch for selecting AUTO Mode (No Handshake Signal), DSR+ Mode (+12V Control) and DSR-Model (-_12V Control) for co

JSTL-JSP Standard Tag Library part 1

Evolution of JSTL: Java is a flexible, general-purpose programming language, JavaServer pages(JSP) depends on java but hides some of the hard details of writing full- fledged programs.  The JSP Standards Tag Library(JSTL) builds on top of JSP, making it even easier to use. Architecture : In this figure large web applications are designed using java, JSTL, and othe components like databases. In large applications, it's common for requests from web browser to be handled by a java program called a servlet, which interacts with databases and other Java code on the server. The servlet figures out how it wants a response be printed and then forwards the user to the right JSTL page, which takes care of nothing more than presenting information. As JSP grew in popularity, it became clear that different sites' custom tags fell into familiar, frequently used patterns.  For example, many pages needed to loop over data to print tables and lists. Vendors of JSP c