Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Introduction to Object-Relational Data Type Descriptors (ELUG)"
m (New page: <div style="float:right;border:1px solid #000000;padding:5px">__TOC__ Related Topics</div> This sec...) |
m |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 4: | Line 4: | ||
For information on descriptor concepts and features common to more than one type of EclipseLink descriptors, see [[Introduction%20to%20Descriptors%20(ELUG)|Introduction to Descriptors]]. | For information on descriptor concepts and features common to more than one type of EclipseLink descriptors, see [[Introduction%20to%20Descriptors%20(ELUG)|Introduction to Descriptors]]. | ||
− | |||
− | |||
− | |||
− | |||
The object-relational data type paradigm extends traditional relational databases to include object-oriented functions. Oracle, IBM DB2, Informix, and other DBMS databases allow users to store, access, and use complex data in more sophisticated ways.The object-relational data type standard is an evolving standard concerned mainly with extending the database data structures and SQL (SQL 3). | The object-relational data type paradigm extends traditional relational databases to include object-oriented functions. Oracle, IBM DB2, Informix, and other DBMS databases allow users to store, access, and use complex data in more sophisticated ways.The object-relational data type standard is an evolving standard concerned mainly with extending the database data structures and SQL (SQL 3). | ||
Line 16: | Line 12: | ||
For more information, see the following: | For more information, see the following: | ||
− | |||
* [[Creating%20an%20Object-Relational%20Data%20Type%20Descriptor%20(ELUG)|Creating an Object-Relational Data Type Descriptor]] | * [[Creating%20an%20Object-Relational%20Data%20Type%20Descriptor%20(ELUG)|Creating an Object-Relational Data Type Descriptor]] | ||
* [[Configuring%20an%20Object-Relational%20Data%20Type%20Descriptor%20(ELUG)|Configuring an Object-Relational Data Type Descriptor]] | * [[Configuring%20an%20Object-Relational%20Data%20Type%20Descriptor%20(ELUG)|Configuring an Object-Relational Data Type Descriptor]] | ||
Line 27: | Line 22: | ||
[[Category: EclipseLink User's Guide]] | [[Category: EclipseLink User's Guide]] | ||
− | [[Category: | + | [[Category: Release 1]] |
[[Category: Concept]] | [[Category: Concept]] | ||
+ | [[Category: ORM]] |
Latest revision as of 07:54, 20 August 2008
This section provides an overview of object-relational data type descriptors.
For information on descriptor concepts and features common to more than one type of EclipseLink descriptors, see Introduction to Descriptors.
The object-relational data type paradigm extends traditional relational databases to include object-oriented functions. Oracle, IBM DB2, Informix, and other DBMS databases allow users to store, access, and use complex data in more sophisticated ways.The object-relational data type standard is an evolving standard concerned mainly with extending the database data structures and SQL (SQL 3).
Object-relational data type descriptors describe Java objects that you map to special relational database types that correspond more closely to object types. Using these special object-relational data type database types can simplify mapping objects to relational database tables. Not all relational databases support these special object-relational data type database types.
Using object-relational data type descriptors in a relational project, you can configure object-relational data type mappings to these special object-relational data type database data types (see Object-Relational Data Type Mapping Types).
For more information, see the following:
- Creating an Object-Relational Data Type Descriptor
- Configuring an Object-Relational Data Type Descriptor