Native UltraLite for Java User's Guide
  Understanding UltraLite Development

Connecting to a database

Any UltraLite application must connect to a database before it can carry out any operation on the data. This section describes how to write code to connect to an UltraLite database.

To connect to an UltraLite database

1. Create a DatabaseManager object.

   You can create only one DatabaseManager object per application. This object is at the root of the object hierarchy. For this reason, it is often best to declare the DatabaseManager object global to the application.

   The following code creates a DatabaseManager object named dbMgr.

   DatabaseManager dbMgr = new DatabaseManager();

   For more details, see the code in Samples\NativeUltraLiteForJava\Simple\Simple.java under your SQL Anywhere directory, and ianywhere.native_ultralite.DatabaseManager in the API Reference.

2. Declare a Connection object.

   Most applications use a single connection to an UltraLite database and keep the connection open all the time. Multiple connections are only required for multi-threaded data access. For this reason, it is often best to declare the Connection object global to the application.

   static Connection conn;

3. Attempt to open a connection to an existing database.

   • The following code establishes a connection to an existing database held in the mydata.udb file on Windows.

     ConnectionParms parms = new ConnectionParms();
     parms.databaseOnDesktop = "mydata.udb";
     try {
       conn = dbMgr.openConnection( parms );
       // more actions here
     }

   • The method establishes a connection to an existing UltraLite database file and returns that open connection as a Connection object.

   • It is common to deploy a schema file rather than a database file, and to let UltraLite create the database file on the first connection attempt. If no database file exists, you should check for the error and create a database file.

     The following code illustrates how to catch the error when the database file does not exist:

     catch( SQLException econn ) {
       if( econn.getErrorCode() ==
           SQLCode.SQLE_ULTRALITE_DATABASE_NOT_FOUND ){
           // action here
     }

4. If no database exists, create a database and establish a connection to it.

   • The following code carries out this task on Windows, using a schema file of mydata.usm.

     CreateParms parms = new CreateParms();
     parms.databaseOnDesktop = "mydata.udb";
     parms.schema.schemaOnDesktop = "mydata.usm";
     try {
        conn = dbMgr.createDatabase( parms );
     }

Example 

The following code opens a connection to an UltraLite database named mydata.udb.

CreateParms parms = new CreateParms();
parms.databaseOnDesktop = "mydata.udb";
parms.schema.schemaOnDesktop = "mydata.usm";
try {
  conn = dbMgr.openConnection( parms );
  System.out.println(
    "Connected to an existing database." );
}
catch( SQLException econn ) {
  if( econn.getErrorCode() ==
      SQLCode.SQLE_DATABASE_NOT_FOUND ){
    conn = dbMgr.createDatabase( parms );
    System.out.println(
    "Connected to a new database." );
  } else {
    throw econn;
  }
}

In general, you will want to specify a more complete path to the file.

For more details, see the code in Samples\NativeUltraLiteForJava\Simple\Simple.java under your SQL Anywhere directory, and ianywhere.native_ultralite.DatabaseManager in the API Reference.

Using the Connection object 

Properties or methods of the Connection object govern global application behavior, including the following:

• Commit behavior    By default, UltraLite applications are in autocommit mode. Each insert, update, or delete statement is committed to the database immediately. You can also set Connection.autoCommit to false to build transactions into your application.

  For more information, see Transaction processing in UltraLite.

• User authentication    You can change the user ID and password for the application from the default values of DBA and SQL by using methods to Grant and Revoke connection permissions. Each application can have a maximum of four user IDs.

  For more information, see User authentication.

• Synchronization    A set of objects governing synchronization are accessed from the Connection object.

  For more information, see the API Reference in the online documentation.

• Tables    UltraLite tables are accessed using methods of the Connection application.

• Prepared statements    A set of objects is provided to handle the execution of dynamic SQL statements and to navigate result sets.

For more information, see Connection.SyncParms and Connection.SyncResult in the API Reference in the online documentation.

Multi-threaded applications 

Each Connection and all objects created from it should be used on a single thread. If you need to have multiple threads accessing the UltraLite database, then each thread should have its own connection.