Derby application developers use the Java Database Connectivity (JDBC) API, the application programming interface that makes it possible to access relational databases from Java programs.
The JDBC API is part of the Java Platform, Standard Edition and is not specific to Derby. It consists of the java.sql and javax.sql packages, which contain classes and interfaces that make it possible to access databases (from a number of different vendors, not just Derby) from a Java application.
To develop Derby applications successfully, you will need to learn the JDBC API. This section does not teach you how to program with the JDBC API.
This section covers the details of application programming that are specific to Derby applications. For example, all JDBC applications typically start their DBMS's JDBC driver and use a connection URL to connect to a database. This section gives you the details of how to start Derby's JDBC driver and how to work with Derby's connection URL to accomplish various tasks. It also covers essential Derby concepts such as the Derby system.
You will find reference information about the particulars of Derby's implementation of the JDBC API in the Derby Reference Manual.
Derby application developers will need to learn SQL. SQL is the standard query language used with relational databases and is not tied to a particular programming language. No matter how a particular RDBMS has been implemented, the user can design databases and insert, modify, and retrieve data using the standard SQL statements and well-defined data types.
SQL is standardized by ANSI and ISO; Derby supports entry-level SQL as well as some higher-level features. Entry-level SQL is a subset of the full SQL specified by ANSI and ISO that is supported by nearly all major DBMSs today.
This section does not teach you SQL. You will find reference information about the particulars of Derby's implementation of SQL in the Derby Reference Manual.
Derby implements the JDBC API so as to allow Derby to serve as a resource manager in a Java EE compliant system.
When an application embeds Derby, application users take on the role of database administrator and must maintain the integrity of the database. See "Part Two: Derby Administration Guide" in the Derby Server and Administration Guide for information on administrative tasks such as backing up and restoring databases. In particular, see the topic "Maintaining database integrity" for information on preventing database corruption. You will need to make this information available to your users.