Advanced Properties

URL pattern - A pattern used to construct the connection URL. In most cases you will not need to change this, however you can customize it as required. The ${databaseName} and ${hostPort} place holders will be substituted with actual values at runtime. This is automatically set to work with the default driver class using the driver manager mechanism (see below). If you wish to use a DataSource, set this to be the URL used to lookup the DataSource in JNDI.

Default primary key columns - In the (rare) case where there is no primary key specified by the database, you can set the primary key based on the leading columns in the table. For example, if you specify a 1, the primary key will be set to the first column in the table (when not specified otherwise by the database). If you specify -1 (the default), then all of the columns in the table will be considered the primary key.

Driver selection - Specify Driver Manager to use a JDBC driver class that is on the classpath or built in. Specify Data Source if you wish to use a JNDI lookup using the specified URL pattern to get the DataSource.

Driver class - The class name of the JDBC driver to use. Each database type has a default driver class, and the Jar file that contains the driver is automatically included in the product, both at design and runtime. If you wish to use your own driver, modify the project's classpath (see Edit Classpath) below so that you can test it in the designer. At runtime, make sure the driver class is available on the classpath (the project's classpath is used only at design time).

XA DataSource driver class - The class name of the XA data source that is provided when distributed transaction support is required. Like the driver class, this is set by default to a class automatically included.

Hibernate dialect class - The class name of the Hibernate dialect class that is used to handle SQL translation for the database.

Hibernate metadata dialect class - The class name of the Hibernate metadata dialect class to handle issues when reading database metadata.

Edit Classpath - Use this to change the classpath that is associated with the project containing the database. You can also change the project's classpath in the project properties (from the Repository navigator). You would change the classpath if you want to test with a database driver for example that is not built in.