JDBC Short Course The goal of this course is to provide an introduction to the JDBC interface for connecting Java programs with SQL-based databases. The course is interwoven with flexible exercises that, together with the course text, allow programmers to tailor the learning process to their particular learning style.
Although there is a short primer on SQL, this course assumes that you are familiar with relational databases and SQL. In particular, the student should know how to define a table in the database they will be using for the exercises.
JDBC 2.0 Fundamentals The exercises in the JDBC tutorial require you to understand, modify, and build Java programs at approximately the intermediate level, although complete solutions are always given. In addition, the reader should have at least a minimal understanding of Relational Database Management Systems (RDBMS) and Structured Query Language (SQL). The SQL Primer and Resources sections of the Appendices contain information, links, and book references to help provide this background.
JDBC(TM) Database Access JDBCTM was designed to keep simple things simple. This means that the JDBC API makes everyday database tasks, like simple SELECT statements, very easy. This trail will walk you through examples of using JDBC to execute common SQL statements, letting you see for yourself how easy it is to use the basic JDBC API.
JDBC Basics covers the JDBC 1.0 API, which is included in JDK tm 1.1. The second part covers the JDBC 2.0 API, which is part of the JDK 1.2 release. It also briefly describes the JDBC extension API, which, like other standard extensions, will be released independently.
JDBC Basics In this lesson you will learn the basics of the JDBC API. We start by giving you set up instructions in Getting Started , Setting Up a Database , and Establishing a Connection . The next sections discuss how to create and update tables, use joins, transactions and stored procedures. The final sections give instructions on how to complete your JDBC application and how to convert it to an applet.
This lesson covers the JDBC 1.0 API, which is included in JDK tm 1.1, and note where procedures have changed in JDBC 2.0, which is included in JDK 1.2. For coverage of JDBC 2.0 and more advanced
Integrating Databases with Java via JDBC The network-oriented nature of Java makes it an ideal candidate for client/server computing, especially now that the ability to integrate it with popular commercial Database Management Systems (DBMS) is in the making. I have heard people question the validity of Java for formal application development. Many users are confused as to the nature of Java and adhere to the notion that it is useful only for making simple animation and small applets for the Web. This is like saying that your heavy-duty Dodge Ram pickup is useful only for taking you to the neighborhood grocery store.
JDBC Technology JDBC technology is an API (included in both J2SE and J2EE releases) that provides cross-DBMS connectivity to a wide range of SQL databases and access to other tabular data sources, such as spreadsheets or flat files. With a JDBC technology-enabled driver, you can connect all corporate data even in a heterogeneous
new in JDBC 3.0 The Java Database Connectivity (JDBC) 3.0 specification builds on an already solid foundation by adding several new features that address a number of areas of missing functionality. Both the java.sql and, for the first time, the javax.sql packages will be included in the Java 1.4 platform, currently in beta. Java developers will be able to take advantage of the enhancements when it is released later this year, which makes this a good time to start understanding the changes.
the JDBCI and API
The material in this chapter is an updated excerpt from JDBCTM API Tutorial and Reference, Second Edition: Universal Data Access for the JavaTM 2 Platform, published by Addison Wesley, ISBN 0-201-43328-1. This document is intended as an overview of the major interfaces and classes and therefore does not cover all of the new features in the JDBCtm 3.0 API. For a more hands-on
approach. The JDBCTM API is the application programming interface that provides universal data access for the JavaTM platform. In other words, you use the JDBC API to work with a relational database or other source of data in an application written in the Java programming language.
JDBCI Advanced Tutorial The JDBC 2.0 API includes many new features in the java.sql package as well as the new Standard Extension package, javax.sql. This new JDBC API moves Java applications into the world of heavy-duty database computing. New features in the java.sql package include support for SQL3 data types, scrollable result sets, programmatic updates, and batch updates. The new JDBC Standard Extension API, an integral part of Enterprise JavaBeans (EJB) technology, allows you to write distributed transactions that use connection pooling, and it also makes it possible to connect to virtually any tabular data source, including files and spread sheets.
Eliminate JDBC overhead While developing a small suite of J2EE (Java 2 Platform, Enterprise Edition) applications for my company recently, I grew frustrated with the bloated process of executing and handling SQL calls. I was sure that somebody in the Java developer family must have developed a framework to clean up the process. Yet searches on such terms as "Java SQL framework" and "JDBC [Java Database Connectivity] framework" yielded no satisfactory results.
JDBC drivers in the wild
Why should you consider Java Database Connectivity (JDBC) drivers apart from the JDBC-ODBC Bridge? What level of JDBC driver is suited for your application? What parameters should you use for evaluating a JDBC driver? This article evaluates various JDBC drivers and answers these questions.
While writing JDBC applications, developers generally start with JDBC-ODBCBridge to connect to databases. But when an application reaches some advanced stage, for example, when it needs to support multithreading, the JDBC-ODBCBridge poses a few problems. So, the need arises for a robust JDBC driver.
JDBC Drivers Software drivers, if I may borrow a quote from Rodney Dangerfield, "Don't get no respect." Most developers think about drivers as minor utilities with limited functionality. But drivers often do more than serve as simple data translators or pipes. They have important features that can impact both the performance and the functionality of your applications.
Java developers often require access to a variety of data sources, including relational databases. JDBC drivers connect Java programs to these data sources using the JDBC standard. Before JDBC, Java developers accessing data sources, such as relational databases, were forced to wrestle with complex SQL statements to write applications with intensive database transactions. So, Sun Microsystems and DataDirect Technologies (formerly the DataDirect division of MERANT) developed JDBC as an API intended to make it easier to write Java applications that could access a variety of data sources.
SQL connecton / J MySQL Connector/J is a native Java driver that converts JDBC (Java Database Connectivity) calls into the network protocol used by the MySQL database. It lets developers working with the Java programming language easily build programs and applets that interact with MySQL and connect all corporate data, even in a heterogeneous environment. MySQL Connector/J is a Type IV JDBC driver and has a complete JDBC feature set that supports the capabilities of
Prepared Statement Many Java programs' success depends on an optimized method of accessing a JDBC (Java Database Connectivity) database known as a PreparedStatement. Debugging such statements can prove troublesome because you cannot retrieve a PreparedStatement's command or any of its associated parameters. In this article, Bob Byron and Troy Thompson show how to save debugging time by using a few strategic classes. Most importantly, you need to change just three lines of code.
JDBC transaction performance tips JDBC Performance Tips (targeted at AS/400, but generically applicable) (Page last updated February 2001, Added 2001-03-21, Authors Richard Dettinger and Mark Megerian, Publisher IBM).
Tips. If you are not using stored procedures or triggers, turn off autocommit. All transaction levels operate faster with autocommit turned off, and doing this means you must code commits. Coding commits while leaving autocommit on will result in extra commits being done for every db operation.