This section outlines the main goals for the JDBC 2.0 API.
2.1 Leverage the strengths of the JDBC 1.0 and Java APIs
One of the important strengths of the JDBC 1.0 API is that it is relatively easy to use.
This ease-of-use is in some respects due to the Java language, which gives JDBC a "hi-
level" flavor, despite the fact that it is a call-level interface. For example, users of the
JDBC 1.0 API aren't required to understand low-level memory-management details, or
byte-alignment, or data alignment details when transferring data to and from the database.
Despite being easy to use, the JDBC API gives Java developers access to a powerful set
of database capabilities. JDBC technology can be used to build sophisticated, real-
world applications. The JDBC 2.0 API must continue to strike the proper balance between
ease-of-use and providing a rich set of functionality.
2.2 Maintain compatibility with JDBC 1.0 applications and drivers
Existing JDBC drivers and the Java applications that use them shall continue to work-
unchanged-in a Java virtual machine that supports the JDBC 2.0 API. Applications
that don't use any of the new features of the JDBC 2.0 API do not require any changes
to continue running. It should be straightforward for existing applications to migrate to
the new JDBC API.
2.3 Keep pace with the Java platform
The Java Platform has matured since the first release of the JDBC API. Some of the new
Java APIs that are important for the JDBC 2.0 API are: the Java Transaction Service
(JTS), the Java Naming and Directory Interface (JNDI), JavaBeans, Enterprise JavaBeans
(EJB), and Internationalization. The JDBC 2.0 API must leverage these other
Java APIs and support them well.
The most important new Java API for JDBC is JavaBeans. When the JDBC API was
first released there was no component model for the Java platform. The JDBC API
should provide a foundation for developers creating data-aware JavaBeans components.
The JDBC API is a good place to provide this standard component foundation
since data access is a ubiquitous aspect of most applications. A new RowSet type has
been added to the JDBC Standard Extension API to meet this goal. Chapter 4 discusses
the differences between the JDBC 2.0 core and JDBC 2.0 Standard Extension APIs.
2.5 Advanced Database Features
There are some important features provided by databases that are not supported by the
JDBC 1.0 API, like scrollable cursors and advanced data types, such as Binary Large
OBjects (BLOBS). The JDBC 2.0 API must support these advanced features.
The JDBC API should provide a framework that allows developers to access instances
of user-defined data types that are stored in a database. The JDBC 2.0 API supports
both databases that provide storage for Java objects, and databases that store SQL3
The JDBC API should provide some basic support for access to non-SQL tabular data,
such as data stored in files. The JDBC Standard Extension API provides some limited
support for tabular data. See Chapter 4 for a discussion of the differences between the
JDBC 2.0 core and JDBC 2.0 Standard Extension APIs.
Contents | Prev | Next
Copyright © 1996, 1997 Sun Microsystems, Inc. All rights reserved.