Difference between revisions of "Configuring a Relational Project (ELUG)"

Latest revision as of 11:25, 18 July 2012

For the latest EclipseLink documentation, please see http://www.eclipse.org/eclipselink/documentation/

This section describes the various components that you must configure in order to use a relational project.

This section also describes logging into a database during development when using Workbench. For more information, see Logging In to the Database.

For information on how to create relational projects, see Creating a Relational Project.

This table lists the configurable options for relational projects. In addition to the configurable options described here, you must also configure the base class options described in Configuring a Project.

For more information, see Introduction to Relational Projects.

Configuring Relational Database Platform at the Project Level

For each relational project, you must specify the database platform (such as Oracle Database 10g). This platform configuration is overridden by the session login, if configured.

For more information, see the following:

• Configuring a Relational Database Platform at the Session Level
• Data Source Platform Types

How to Configure Relational Database Platform at the Project Level Using Workbench

To specify the database platform of a relational project, use this procedure:

1. Select the database object in the Navigator. The Database property sheet appears.
   Database Property Sheet, Database Platform Options
   
2. Complete the Database Platform option on the property sheet.
3. Click Change to select a new database platform for the project. For more information, see Data Source Platform Types.

Configuring Sequencing at the Project Level

Sequencing allows EclipseLink to automatically assign the primary key or ID of an object when the object is inserted.

You configure EclipseLink sequencing at the project or session level to tell EclipseLink how to obtain sequence values: that is, what type of sequences to use.

In a POJO project, you can configure a session directly: in this case, you can use a session-level sequence configuration to override project-level sequence configuration, on a session-by-session basis), if required (see .

Using the Workbench, you can configure Table Sequencing and native sequencing (see Native Sequencing with an Oracle Database Platform and Native Sequencing with a Non-Oracle Database Platform), and you can configure a preallocation size that applies to all sequences (see Sequencing and Preallocation Size).

Using Java, you can configure any sequence type that EclipseLink supports (see Sequencing Types). You can create any number and combination of sequences. You can create a sequence object explicitly or use the default sequence that the platform creates. You can associate the same sequence with more than one descriptor and you can configure a separate preallocation size for each descriptor's sequence.

After configuring the sequence type at the project (or session) level, to enable sequencing, you must configure a descriptor with a sequence field and a sequence name.

For more information about sequencing, see Sequencing in Relational Projects.

How to Configure Sequencing at the Project Level Using Workbench

To specify the sequencing information for the project, use this procedure:

1. Select the project object in the Navigator.
2. Select the Sequencing tab in the Editor. The Sequencing tab appears.
   Sequencing Tab
   
3. Complete each field on Sequencing tab.

Use this table to enter data in the following fields to configure the sequencing information:

How to Configure Sequencing at the Project Level Using Java

Using Java, you can configure a project to use multiple, different sequences, as this exmaple shows.

Configuring Sequencing at the Project Level in Java

 // Enable native sequencing for the project as the default. Configured the default
 // preallocation size'''
 project.getLogin().useNativeSequencing();
 project.getLogin().setSequencePreallocationSize(50);
 
 // Configure the EMP_SEQ to not use preallocation
 DefaultSequence empSequence = new DefaultSequence("EMP_SEQ", 1);
 project.getLogin().addSequence(empSequence);
 
 // Configure the PROJ_SEQ to use a seperate sequence table
 UnarySequence projSequence = new UnarySequence("PROJ_SEQ_TAB", "COUNTER");
 project.getLogin().addSequence(projSequence);

Configuring Login Information at the Project Level

This section describes how to define a login to a relational database. After you define a login, you must designate its role.

After you create a login and specify it as a development login, you can log in to a database instance.

How to Configure Login Information at the Project Level UsingWorkbench

To create or edit a database login, use this procedure:

1. Select the database object in the Navigator. The Database property sheet appears.
   Database Property Sheet, Database Login Fields
   
2. Click Add to create a new Defined Login.
3. Complete the Database Login fields on the property sheet.

Use this table to enter data in the following fields on the Database property sheet to configure the database login:

See Also:

Configuring Login Information at the Project Level

Configuring Relational Database Platform at the Project Level

Configuring Development and Deployment Logins

Configuring Development and Deployment Logins

This section describes how to designate a defined login's role. For information on how to define a login, see Configuring Login Information at the Project Level. EclipseLink recognizes the following login roles:

• Development Role
• POJO Session Role

Development Role

While using Workbench to develop a project (see Development Role), you must define a login (see Configuring Login Information at the Project Level) and designate it as the development login. The development login is stored in the EclipseLink project file. Workbench use the information in the development login whenever you perform a data source operation from within Workbench. For example, when you read or write schema information from or to a data source during application development, the development login information is never written to a sessions.xml or project.xml file and is overridden by the deployment login (or the session login) at run time.

For more information on how to use a development login to connect to a database, see Logging In to the Database.

POJO Session Role

If you are creating a POJO project, we recommend that you use the sessions.xml file to store the sessions your project uses at run time (see Data Source Login Types).

How to Configure Development and Deployment Logins Using Workbench

To specify different development and deployment database logins, use this procedure:

1. Select the database object in the Navigator. The Database property sheet appears.
   Database Property Sheet, Development and Deployment Login Options
   
2. Complete the Development and Deployment Login options on the property sheet by selecting from the logins you configured previously.

Use this table to enter data in the following fields on the Database property sheet to configure the login:

See Also:

Configuring Development and Deployment Logins

Development Role

Logging In to the Database

Using Workbench, after you create a login and specify it as a development login, you can log in to a database instance.

You must log in to the database before importing or exporting table information.

To log in to the database using Workbench, use one of the following procedures:

• Select the database object in the Navigator and click Login Database Login button. Workbench logs in to the database.
• Right-click on the database object in the Navigator and choose Log In to Database from the context menu, or choose Selected > Log In to Database from the menu.

The database icon in the Navigator window changes to indicate you are now logged in to the database.

Configuring Named Query Parameterized SQL and Statement Caching at the Project Level

You can configure EclipseLink to use parameterized SQL (parameter binding) and prepared statement caching for all named queries and finders.

By default, EclipseLink uses parameterized SQL.

The use of parameterized SQL lets you create and store queries that are complete except for one or more bound parameters. The EclipseLink runtime binds the current parameter values when executing the query. This approach avoids the preparation of SQL execution and, thus, improves the performance of frequently executed SQL statements.

This section describes configuring parameterized SQL and statement caching options at the project level. This configuration applies to all named queries or finders (see Named Queries) you create on the descriptors in this project–not to all queries in general or write operations.

You can also configure parameterized SQL and statement caching options at the named query or finder-level to override this project-level configuration on a query-by-query basis (see Configuring Named Query Options) or at the session login-level (see Configuring JDBC Options).

For more information, see How to Use Parameterized SQL (Parameter Binding) and Prepared Statement Caching for Optimization.

This table summarizes which projects support parameterized SQL and statement caching configuration.

Project Support for Default Named Query Caching and Binding

How to Configure Named Query Parameterized SQL and Statement Caching at the Project Level Using Workbench

To specify the named query options, use this procedure:

1. Select the project object in the Navigator.
2. Select the Defaults tab in the Editor. The Defaults tab appears.
   Defaults Tab, Named Queries Options
   
3. Complete the Named Query options on the tab.

Use this table to enter data in following fields on the Defaults tab to specify the named query options for newly created descriptors.:

See Also:

Configuring Named Query Parameterized SQL and Statement Caching at the Project Level

Configuring a Project

Configuring Table Generation Options

Using Workbench, you can configure options that apply when you generate database tables from the descriptors you define in your Workbench project. The resulting tables and columns will conform to the naming restrictions of the project's target database.

How to Configure Table Generation Options Using Workbench

To specify the default table generation options, use this procedure:

1. Select the project object in the Navigator.
2. Select the Options tab in the Editor. The Options tab appears.
   Options Tab, Table Generation Options
   
3. Complete the fields on the Table Generation defaults on the tab.

Use this table to enter data in the following fields to specify the default export and generation options.

Configuring Table Creator Java Source Options

Using Workbench, you can configure options that apply when you export Java source code that you can use to create database tables.

How to Configure Table Creator Java Source Options Using Workbench

To specify the default Java code generation options, use this procedure:

1. Select the project object in the Navigator.
2. Select the Options tab in the Editor. The Options tab appears.
   Options Tab, Table Creator Java Source Options
   
3. Complete the fields on the Table Creator Java Source defaults on the tab.

Use this table to enter data in the following fields to specify the default table creator options.

Configuring Project Java Source Code Options

Using Workbench, you can export a project as Java source. You can configure the class name and root directory that Workbench uses when exporting the project to Java source code.

For more information on exporting a project as Java source, see How to Export Project Java Source Using Workbench.

How to Configure Project Java Source Code Options Using Workbench

To specify the default Java code generation options, use this procedure:

1. Select the project object in the Navigator.
2. Select the Options tab in the Editor. The Options tab appears.
   Options Tab, Project Java Source Options
   Options Tab, Project Java Source Options
3. Complete the fields on the Project Java Source defaults on the tab.

Use this table to enter data in the following fields to specify the default export and generation options:

Copyright Statement