Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Configuring an Object-Relational Data Type Mapping (ELUG)"

m (Configuring Structure Name)
m
Line 5: Line 5:
 
For information on how to configure EclipseLink mappings options common to two or more mapping types, see [[Configuring%20a%20Mapping%20(ELUG)|Configuring a Mapping]].
 
For information on how to configure EclipseLink mappings options common to two or more mapping types, see [[Configuring%20a%20Mapping%20(ELUG)|Configuring a Mapping]].
  
For information on how to create EclipseLink mappings, see [[Creating%20a%20Mapping%20(ELUG)#Creating a Mapping]].
+
For information on how to create EclipseLink mappings, see [[Creating%20a%20Mapping%20(ELUG)|Creating a Mapping]].
  
  
Line 25: Line 25:
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Structure Mapping|Object-relational data type structure mapping ]]
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Structure Mapping|Object-relational data type structure mapping ]]
 
| headers="r2c1-t2 r1c2-t2" align="left" |
 
| headers="r2c1-t2 r1c2-t2" align="left" |
[Configuring%20an%20Object-Relational%20Data%20Type%20Structure%20Mapping%20(ELUG)#Chapter 46, "Configuring an Object-Relational Data Type Structure Mapping"]<br>
+
[[Configuring%20an%20Object-Relational%20Data%20Type%20Structure%20Mapping%20(ELUG)|Configuring an Object-Relational Data Type Structure Mapping]]<br>
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r3c1-t2" headers="r1c1-t2" align="left" |
 
| id="r3c1-t2" headers="r1c1-t2" align="left" |
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Reference Mapping|Object-relational data type reference mapping ]]
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Reference Mapping|Object-relational data type reference mapping ]]
 
| headers="r3c1-t2 r1c2-t2" align="left" |
 
| headers="r3c1-t2 r1c2-t2" align="left" |
[Configuring%20an%20Object-Relational%20Data%20Type%20Reference%20Mapping%20(ELUG)#Chapter 47, "Configuring an Object-Relational Data Type Reference Mapping"]<br>
+
[[Configuring%20an%20Object-Relational%20Data%20Type%20Reference%20Mapping%20(ELUG)|Configuring an Object-Relational Data Type Reference Mapping]]<br>
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r4c1-t2" headers="r1c1-t2" align="left" |
 
| id="r4c1-t2" headers="r1c1-t2" align="left" |
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Array Mapping|Object-relational data type array mapping ]]
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Array Mapping|Object-relational data type array mapping ]]
 
| headers="r4c1-t2 r1c2-t2" align="left" |
 
| headers="r4c1-t2 r1c2-t2" align="left" |
[Configuring%20an%20Object-Relational%20Data%20Type%20Array%20Mapping%20(ELUG)#Chapter 48, "Configuring an Object-Relational Data Type Array Mapping"]<br>
+
[[Configuring%20an%20Object-Relational%20Data%20Type%20Array%20Mapping%20(ELUG)|Configuring an Object-Relational Data Type Array Mapping]]<br>
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r5c1-t2" headers="r1c1-t2" align="left" |
 
| id="r5c1-t2" headers="r1c1-t2" align="left" |
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Object Array Mapping|Object-relational data type object array mapping]]
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Object Array Mapping|Object-relational data type object array mapping]]
 
| headers="r5c1-t2 r1c2-t2" align="left" |
 
| headers="r5c1-t2 r1c2-t2" align="left" |
[Configuring%20an%20Object-Relational%20Data%20Type%20Object%20Array%20Mapping%20(ELUG)#Chapter 49, "Configuring an Object-Relational Data Type Object Array Mapping"]<br>
+
[[Configuring%20an%20Object-Relational%20Data%20Type%20Object%20Array%20Mapping%20(ELUG)|Configuring an Object-Relational Data Type Object Array Mapping]]<br>
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r6c1-t2" headers="r1c1-t2" align="left" |
 
| id="r6c1-t2" headers="r1c1-t2" align="left" |
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Nested Table Mapping|Object-relational data type nested table mapping ]])
 
[[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Nested Table Mapping|Object-relational data type nested table mapping ]])
 
| headers="r6c1-t2 r1c2-t2" align="left" |
 
| headers="r6c1-t2 r1c2-t2" align="left" |
[Configuring%20an%20Object-Relational%20Data%20Type%20Nested%20Table%20Mapping%20(ELUG)#Chapter 51, "Configuring an Object-Relational Data Type Nested Table Mapping"]<br>
+
[[Configuring%20an%20Object-Relational%20Data%20Type%20Nested%20Table%20Mapping%20(ELUG)|Configuring an Object-Relational Data Type Nested Table Mapping]]<br>
 
|}
 
|}
  
<br>
+
 
  
 
For more information, see the following:
 
For more information, see the following:
 
+
* [[Introduction%20to%20Mappings%20(ELUG)|Introduction to Mappings]]
* [Introduction%20to%20Mappings%20(ELUG)#Chapter 16, "Introduction to Mappings"]
+
* [[Introduction%20to%20Relational%20Mappings%20(ELUG)|Introduction to Relational Mappings]]
* [Introduction%20to%20Relational%20Mappings%20(ELUG)#Chapter 32, "Introduction to Relational Mappings"]
+
  
  
  
 
==Configuring Common Object-Relational Data Type Mapping Options==
 
==Configuring Common Object-Relational Data Type Mapping Options==
 
+
Thist able lists the configurable options shared by two or more object-relational data type mapping types. In addition to the configurable options described here, you must also configure the options described for the specific object-relational data type mapping types (see [[Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Mapping Types|Object-Relational Data Type Mapping Types]]), as shown in [[#Table 50-1|Configuring Object-Relational Data Type Mappings]].
Thist able lists the configurable options shared by two or more object-relational data type mapping types. In addition to the configurable options described here, you must also configure the options described for the specific object-relational data type mapping types (see [Introduction%20to%20Object-Relational%20Data%20Type%20Mappings%20(ELUG)#Object-Relational Data Type Mapping Types]), as shown in [[#Table 50-1]].
+
  
  
 
<span id="Table 50-2"></span>
 
<span id="Table 50-2"></span>
 
''''' Common Options for Object-Relational Data Type Mappings'''''
 
''''' Common Options for Object-Relational Data Type Mappings'''''
 
+
{| class="RuleFormalMax" dir="ltr" title="Common Options for Object-Relational Data Type Mappings" summary="This table lists the configurable options shated by two or more object relational mapping types and categorizes them as Basic and Advanced and indicates if the option can be configured with the Workbench, Java, or both." width="100%" border="1" frame="border" rules="all" cellpadding="3" frame="border" rules="all"
{| class="RuleFormalMax" dir="ltr" title="Common Options for Object-Relational Data Type Mappings" summary="This table lists the configurable options shated by two or more object relational mapping types and categorizes them as Basic and Advanced and indicates if the option can be configured with the TopLink Mapping Workbench, Java, or both." width="100%" border="1" frame="border" rules="all" cellpadding="3" frame="border" rules="all"
+
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
! id="r1c1-t3" align="left" valign="bottom" | '''Option to Configure'''
 
! id="r1c1-t3" align="left" valign="bottom" | '''Option to Configure'''
! id="r1c2-t3" align="left" valign="bottom" | '''JDeveloper<br>'''
 
 
! id="r1c3-t3" align="left" valign="bottom" | '''Workbench<br>'''
 
! id="r1c3-t3" align="left" valign="bottom" | '''Workbench<br>'''
 
! id="r1c4-t3" align="left" valign="bottom" | '''Java'''
 
! id="r1c4-t3" align="left" valign="bottom" | '''Java'''
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r2c1-t3" headers="r1c1-t3" align="left" |
 
| id="r2c1-t3" headers="r1c1-t3" align="left" |
Reference class (see [[#Configuring Reference Class])
+
[[#Configuring Reference Class|Reference class ]]
| headers="r2c1-t3 r1c2-t3" align="left" |
+
[[Image:unsupport.gif|Unsupported]]<br>
+
 
| headers="r2c1-t3 r1c3-t3" align="left" |
 
| headers="r2c1-t3 r1c3-t3" align="left" |
 
[[Image:unsupport.gif|Unsupported]]<br>
 
[[Image:unsupport.gif|Unsupported]]<br>
Line 82: Line 76:
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r3c1-t3" headers="r1c1-t3" align="left" |
 
| id="r3c1-t3" headers="r1c1-t3" align="left" |
Attribute name (see [[#Configuring Attribute Name])
+
[[#Configuring Attribute Name|Attribute name ]]
| headers="r3c1-t3 r1c2-t3" align="left" |
+
[[Image:unsupport.gif|Unsupported]]<br>
+
 
| headers="r3c1-t3 r1c3-t3" align="left" |
 
| headers="r3c1-t3 r1c3-t3" align="left" |
 
[[Image:unsupport.gif|Unsupported]]<br>
 
[[Image:unsupport.gif|Unsupported]]<br>
Line 91: Line 83:
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r4c1-t3" headers="r1c1-t3" align="left" |
 
| id="r4c1-t3" headers="r1c1-t3" align="left" |
Field name (see [[#Configuring Field Name])
+
[[#Configuring Field Name|Field name ]]
| headers="r4c1-t3 r1c2-t3" align="left" |
+
[[Image:unsupport.gif|Unsupported]]<br>
+
 
| headers="r4c1-t3 r1c3-t3" align="left" |
 
| headers="r4c1-t3 r1c3-t3" align="left" |
 
[[Image:unsupport.gif|Unsupported]]<br>
 
[[Image:unsupport.gif|Unsupported]]<br>
Line 100: Line 90:
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r5c1-t3" headers="r1c1-t3" align="left" |
 
| id="r5c1-t3" headers="r1c1-t3" align="left" |
Structure name (see [[#Configuring Structure Name])
+
[[#Configuring Structure Name|Structure name]]
| headers="r5c1-t3 r1c2-t3" align="left" |
+
[[Image:unsupport.gif|Unsupported]]<br>
+
 
| headers="r5c1-t3 r1c3-t3" align="left" |
 
| headers="r5c1-t3 r1c3-t3" align="left" |
 
[[Image:unsupport.gif|Unsupported]]<br>
 
[[Image:unsupport.gif|Unsupported]]<br>
Line 109: Line 97:
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r6c1-t3" headers="r1c1-t3" align="left" |
 
| id="r6c1-t3" headers="r1c1-t3" align="left" |
Read-only (see [Configuring%20a%20Mapping%20(ELUG)#Configuring Read-Only Mappings])
+
[[Configuring%20a%20Mapping%20(ELUG)#Configuring Read-Only Mappings|Read-only]]
| headers="r6c1-t3 r1c2-t3" align="left" |
+
[[Image:unsupport.gif|Unsupported]]<br>
+
 
| headers="r6c1-t3 r1c3-t3" align="left" |
 
| headers="r6c1-t3 r1c3-t3" align="left" |
 
[[Image:unsupport.gif|Unsupported]]<br>
 
[[Image:unsupport.gif|Unsupported]]<br>
Line 118: Line 104:
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r7c1-t3" headers="r1c1-t3" align="left" |
 
| id="r7c1-t3" headers="r1c1-t3" align="left" |
Method or direct field access (see [Configuring%20a%20Mapping%20(ELUG)#Configuring Method or Direct Field Accessing at the Mapping Level])
+
[[Configuring%20a%20Mapping%20(ELUG)#Configuring Method or Direct Field Accessing at the Mapping Level|Method or direct field access ]]
| headers="r7c1-t3 r1c2-t3" align="left" |
+
[[Image:unsupport.gif|Unsupported]]<br>
+
 
| headers="r7c1-t3 r1c3-t3" align="left" |
 
| headers="r7c1-t3 r1c3-t3" align="left" |
 
[[Image:unsupport.gif|Unsupported]]<br>
 
[[Image:unsupport.gif|Unsupported]]<br>
Line 127: Line 111:
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r8c1-t3" headers="r1c1-t3" align="left" |
 
| id="r8c1-t3" headers="r1c1-t3" align="left" |
Indirection (lazy loading) (see [Configuring%20a%20Mapping%20(ELUG)#Configuring Indirection (Lazy Loading)])
+
[[Configuring%20a%20Mapping%20(ELUG)#Configuring Indirection (Lazy Loading)|Indirection (lazy loading)]]
| headers="r8c1-t3 r1c2-t3" align="left" |
+
[[Image:unsupport.gif|Unsupported]]<br>
+
 
| headers="r8c1-t3 r1c3-t3" align="left" |
 
| headers="r8c1-t3 r1c3-t3" align="left" |
 
[[Image:unsupport.gif|Unsupported]]<br>
 
[[Image:unsupport.gif|Unsupported]]<br>
Line 136: Line 118:
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r9c1-t3" headers="r1c1-t3" align="left" |
 
| id="r9c1-t3" headers="r1c1-t3" align="left" |
Container policy (see [Configuring%20a%20Mapping%20(ELUG)#Configuring Container Policy])
+
[[Configuring%20a%20Mapping%20(ELUG)#Configuring Container Policy|Container policy ]]
| headers="r9c1-t3 r1c2-t3" align="left" |
+
[[Image:unsupport.gif|Unsupported]]<br>
+
 
| headers="r9c1-t3 r1c3-t3" align="left" |
 
| headers="r9c1-t3 r1c3-t3" align="left" |
 
[[Image:unsupport.gif|Unsupported]]<br>
 
[[Image:unsupport.gif|Unsupported]]<br>
Line 145: Line 125:
 
|}
 
|}
  
<br>
+
 
  
 
==Configuring Reference Class==
 
==Configuring Reference Class==
 
 
When mapping an attribute that involves a relationship to another class, you must specify the reference class–the Java class to which the mapped attribute refers.
 
When mapping an attribute that involves a relationship to another class, you must specify the reference class–the Java class to which the mapped attribute refers.
  
Line 156: Line 135:
 
<span id="Table 50-3"></span>
 
<span id="Table 50-3"></span>
 
''''' Mapping Support for Reference Class'''''
 
''''' Mapping Support for Reference Class'''''
 
 
{| class="RuleFormal" dir="ltr" title="Mapping Support for Reference Class" summary="This table summarizes which mappings support Reference Class" width="100%" border="1" frame="border" rules="all" cellpadding="3" frame="border" rules="all"
 
{| class="RuleFormal" dir="ltr" title="Mapping Support for Reference Class" summary="This table summarizes which mappings support Reference Class" width="100%" border="1" frame="border" rules="all" cellpadding="3" frame="border" rules="all"
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
! id="r1c1-t4" align="left" valign="bottom" | '''Mapping'''
 
! id="r1c1-t4" align="left" valign="bottom" | '''Mapping'''
 
! id="r1c2-t4" align="left" valign="bottom" | '''How to Use Workbench'''
 
! id="r1c2-t4" align="left" valign="bottom" | '''How to Use Workbench'''
! id="r1c3-t4" align="left" valign="bottom" | '''[[#How to Configure Reference Class Using Java]<br>'''
+
! id="r1c3-t4" align="left" valign="bottom" | '''[[#How to Configure Reference Class Using Java|Using Java]]<br>'''
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r2c1-t4" headers="r1c1-t4" align="left" |
 
| id="r2c1-t4" headers="r1c1-t4" align="left" |
Line 228: Line 206:
  
 
==Configuring Attribute Name==
 
==Configuring Attribute Name==
 
 
All object-relational data type mappings map an attribute in a Java object to field in the database. The attribute name is the name of the attribute being mapped. The name is as specified in the reference class (see [[#Configuring Reference Class|Configuring Reference Class]]).
 
All object-relational data type mappings map an attribute in a Java object to field in the database. The attribute name is the name of the attribute being mapped. The name is as specified in the reference class (see [[#Configuring Reference Class|Configuring Reference Class]]).
  
Line 241: Line 218:
 
! id="r1c1-t5" align="left" valign="bottom" | '''Mapping'''
 
! id="r1c1-t5" align="left" valign="bottom" | '''Mapping'''
 
! id="r1c2-t5" align="left" valign="bottom" | '''How to Use Workbench'''
 
! id="r1c2-t5" align="left" valign="bottom" | '''How to Use Workbench'''
! id="r1c3-t5" align="left" valign="bottom" | '''[[#How to Configure Attribute Name Using Java]<br>'''
+
! id="r1c3-t5" align="left" valign="bottom" | '''[[#How to Configure Attribute Name Using Java|Using Java]]<br>'''
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r2c1-t5" headers="r1c1-t5" align="left" |
 
| id="r2c1-t5" headers="r1c1-t5" align="left" |
Line 309: Line 286:
  
 
==Configuring Field Name==
 
==Configuring Field Name==
 
 
All object-relational data type mappings require the name of database field to which their specified attribute is mapped. This field name can be the column name of a database table or the name of a field in an object type created on the database.
 
All object-relational data type mappings require the name of database field to which their specified attribute is mapped. This field name can be the column name of a database table or the name of a field in an object type created on the database.
  
Line 322: Line 298:
 
! id="r1c1-t6" align="left" valign="bottom" | '''Mapping'''
 
! id="r1c1-t6" align="left" valign="bottom" | '''Mapping'''
 
! id="r1c2-t6" align="left" valign="bottom" | '''How to Use Workbench'''
 
! id="r1c2-t6" align="left" valign="bottom" | '''How to Use Workbench'''
! id="r1c3-t6" align="left" valign="bottom" | '''[[#How to Configure Field Name Using Java]]<br>'''
+
! id="r1c3-t6" align="left" valign="bottom" | '''[[#How to Configure Field Name Using Java|Using Java]]<br>'''
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r2c1-t6" headers="r1c1-t6" align="left" |
 
| id="r2c1-t6" headers="r1c1-t6" align="left" |
Line 365: Line 341:
  
 
===How to Configure Field Name Using Java===
 
===How to Configure Field Name Using Java===
 
 
Use the object-relational data type mapping method <tt>setFieldName</tt> to specify the database field to which the attribute is mapped.
 
Use the object-relational data type mapping method <tt>setFieldName</tt> to specify the database field to which the attribute is mapped.
  
Line 403: Line 378:
 
! id="r1c1-t7" align="left" valign="bottom" | '''Mapping'''
 
! id="r1c1-t7" align="left" valign="bottom" | '''Mapping'''
 
! id="r1c3-t7" align="left" valign="bottom" | '''How to Use Workbench'''
 
! id="r1c3-t7" align="left" valign="bottom" | '''How to Use Workbench'''
! id="r1c4-t7" align="left" valign="bottom" | '''[[#How to Configure Structure Name Using Java]<br>'''
+
! id="r1c4-t7" align="left" valign="bottom" | '''[[#How to Configure Structure Name Using Java|Using Java]]<br>'''
 
|- align="left" valign="top"
 
|- align="left" valign="top"
 
| id="r2c1-t7" headers="r1c1-t7" align="left" |
 
| id="r2c1-t7" headers="r1c1-t7" align="left" |

Revision as of 12:17, 4 December 2007

This section describes how to configure an object-relational data type mapping.

For information on how to configure EclipseLink mappings options common to two or more mapping types, see Configuring a Mapping.

For information on how to create EclipseLink mappings, see Creating a Mapping.


Introduction to Object-Relational Data Type Mapping Configuration

This table lists the types of object-relational data type mappings that you can configure and provides a cross-reference to the type-specific chapter that lists the configurable options supported by that type.


Configuring Object-Relational Data Type Mappings

If you are creating... See Also...

Object-relational data type structure mapping

Configuring an Object-Relational Data Type Structure Mapping

Object-relational data type reference mapping

Configuring an Object-Relational Data Type Reference Mapping

Object-relational data type array mapping

Configuring an Object-Relational Data Type Array Mapping

Object-relational data type object array mapping

Configuring an Object-Relational Data Type Object Array Mapping

Object-relational data type nested table mapping )

Configuring an Object-Relational Data Type Nested Table Mapping


For more information, see the following:


Configuring Common Object-Relational Data Type Mapping Options

Thist able lists the configurable options shared by two or more object-relational data type mapping types. In addition to the configurable options described here, you must also configure the options described for the specific object-relational data type mapping types (see Object-Relational Data Type Mapping Types), as shown in Configuring Object-Relational Data Type Mappings.


Common Options for Object-Relational Data Type Mappings

Option to Configure Workbench
Java

Reference class

Unsupported

Supported

Attribute name

Unsupported

Supported

Field name

Unsupported

Supported

Structure name

Unsupported

Supported

Read-only

Unsupported

Supported

Method or direct field access

Unsupported

Supported

Indirection (lazy loading)

Unsupported

Supported

Container policy

Unsupported

Supported


Configuring Reference Class

When mapping an attribute that involves a relationship to another class, you must specify the reference class–the Java class to which the mapped attribute refers.

This table summarizes which object-relational data type mappings support this option.


Mapping Support for Reference Class

Mapping How to Use Workbench Using Java

Object-relational data type structure mapping

Unsupported.

Supported.

Object-relational data type reference mapping

Unsupported.

Supported.

Object-relational data type array mapping

Unsupported.

Unsupported.

Object-relational data type object array mapping

Unsupported.

Supported.

Object-relational data type nested table mapping

Unsupported.

Supported.



How to Configure Reference Class Using Java

Use org.eclipse.persistence.mappings.ForeignReferenceMapping method setReferenceClass to specify the target class of the attribute being mapped.

Tihs example shows how to use this method with a ReferenceMapping that maps the manager attribute of the Employee class.


Configuring Reference Class in Java

public void customize(ClassDescriptor descriptor) { 
    ReferenceMapping managerMapping = new ReferenceMapping();
    managerMapping.setReferenceClass("Employee.class"); // set reference class
    managerMapping.setAttributeName("manager");

    // add this mapping to descriptor
    descriptor.addMapping (managerMapping);
}


For more information, see the EclipseLink API Reference.


Configuring Attribute Name

All object-relational data type mappings map an attribute in a Java object to field in the database. The attribute name is the name of the attribute being mapped. The name is as specified in the reference class (see Configuring Reference Class).

This table summarizes which object-relational data type mappings support this option.


Mapping Support for Attribute Name

Mapping How to Use Workbench Using Java

Object-relational data type structure mapping

Supported

Supported.

Object-relational data type reference mapping

Supported

Supported.

Object-relational data type array mapping

Supported

Supported.

Object-relational data type object array mapping

Supported

Supported.

Object-relational data type nested table mapping

Supported

Supported.



How to Configure Attribute Name Using Java

Use org.eclipse.persistence.mappings.DatabaseMapping method setAttributeName to specify the name of the attribute being mapped.

This table shows how to use this method with a ReferenceMapping that maps the manager attribute of the Employee class.


Configuring Attribute Name in Java

public void customize(ClassDescriptor descriptor) { 
    ReferenceMapping managerMapping = new new ReferenceMapping();
    managerMapping.setReferenceClass("Employee.class"); 
    managerMapping.setAttributeName("manager"); // set attribute name

    // add this mapping to descriptor
    descriptor.addMapping (managerMapping);
}


For more information, see the EclipseLink API Reference.


Configuring Field Name

All object-relational data type mappings require the name of database field to which their specified attribute is mapped. This field name can be the column name of a database table or the name of a field in an object type created on the database.

Thist able summarizes which object-relational data type mappings support this option.


Mapping Support for Field Name

Mapping How to Use Workbench Using Java

Object-relational data type structure mapping

Unsupported.

Supported.

Object-relational data type reference mapping

Unsupported.

Supported.

Object-relational data type array mapping

Unsupported.

Supported.

Object-relational data type object array mapping

Unsupported.

Supported.

Object-relational data type nested table mapping

Unsupported.

Supported.



How to Configure Field Name Using Java

Use the object-relational data type mapping method setFieldName to specify the database field to which the attribute is mapped.

This example shows how to use this method with an ObjectArrayMapping that maps the Employee class attribute phone to database field name PHONE_NUMBER.


Configuring Field Name in Java

public void customize(ClassDescriptor descriptor) { 
    ObjectArrayMapping phonesMapping = new ObjectArrayMapping();
    phonesMapping.setReferenceClass("Employee.class");
    phonesMapping.setAttributeName("phone");
    phonesMapping.setFieldName("PHONE_NUMBER"); // set field name

    // add this mapping to descriptor
    descriptor.addMapping (phonesMapping);
}


For more information, see the EclipseLink API Reference.


Configuring Structure Name

Certain object-relational data type mappings require the specification of the data type or structure name of the field being mapped. The structure name is the name of the array or table type that defines the field.

This table summarizes which object-relational data type mappings support this option.


Mapping Support for Structure Name

Mapping How to Use Workbench Using Java

Object-relational data type structure mapping

Unsupported.

Unsupported.

Object-relational data type reference mapping

Unsupported.

Unsupported.

Object-relational data type array mapping

Unsupported.

Supported.

Object-relational data type object array mapping

Unsupported.

Supported.

Object-relational data type nested table mapping )

Unsupported.

Supported.



How to Configure Structure Name Using Java

Use the object-relational data type mapping method setStructureName to specify the structure of the attribute being mapped.

This example shows how to use this method with an ObjectArrayMapping that maps the Employee class attribute phones to database field name PHONE_NUMBERS of type PHONE_ARRAY_TYPE.


Configuring Structure Name in Java

public void customize(ClassDescriptor descriptor) { 
    ObjectArrayMapping phonesMapping = new ObjectArrayMapping();
    phonesMapping.setReferenceClass("Employee.class");
    phonesMapping.setAttributeName("phones");
    phonesMapping.setFieldName("PHONE_NUMBERS");
    phonesMapping.setStructureName("PHONE_ARRAY_TYPE"); // set structure name

    // add this mapping to descriptor
    descriptor.addMapping (phonesMapping);
}


For more information, see the EclipseLink API Reference.



Copyright Statement

Back to the top