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 "Talk:EclipseLink/UserGuide/JPA/Basic JPA Development/Mapping/Relationship Mappings/Collection Mappings/OneToMany"
m |
m |
||
| Line 5: | Line 5: | ||
*Began moving content from old ELUG -- introductory material on 1:1 and 1:M mappings.<br/>--[[User:Rick.sapir.oracle.com|Rick]] 11:51, 24 June 2010 (UTC) | *Began moving content from old ELUG -- introductory material on 1:1 and 1:M mappings.<br/>--[[User:Rick.sapir.oracle.com|Rick]] 11:51, 24 June 2010 (UTC) | ||
| + | |||
| + | ___ | ||
| + | |||
| + | -- [[User:ben.gelernter.oracle.com|Ben Gelernter]] 5/03/11 | ||
| + | |||
| + | : ELUG ref | ||
| + | : I removed these references to ELUG. Return here to see if this information needs to be brought forward into this doc. | ||
| + | ::The last sentence in the note after the graphic was: | ||
| + | :::See [[Configuring%20a%20Mapping%20(ELUG)#Configuring Container Policy|Configuring Container Policy]] for details. | ||
| + | |||
| + | ::The "fetch" row in the table included the following. The ref to ELUG was removed: | ||
| + | :::For more information, see [[Using%20EclipseLink%20JPA%20Extensions%20(ELUG)#What You May Need to Know About EclipseLink JPA Lazy Loading|What You May Need to Know About EclipseLink JPA Lazy Loading]] | ||
| + | |||
| + | ::The very last two sentences in the section were: | ||
| + | :::For more information on EclipseLink direct mappings and relationship mappings, see [[Introduction%20to%20Relational%20Mappings%20(ELUG)#Relational Mapping Types|Relational Mapping Types]]. | ||
| + | |||
| + | :::For more information on EclipseLink one-to-one mappings, see [[Introduction%20to%20Relational%20Mappings%20(ELUG)#One-to-Many Mapping|One-to-Many Mapping]], and for information on how to configure these mappings, see [[Configuring a Relational One-to-Many Mapping (ELUG)|Configuring a Relational One-to-Many Mapping]]. | ||
| + | ---- | ||
Revision as of 15:16, 3 May 2011
This should start by explaining what a OneToMany mapping is, and how it is represented in the database. Ideally a picture of the object/model/database schema. It should explain the three different types (using a join table (default), bi-directional using a mappedBy/target foreign key, unidirectional using a JoinColumn (and issues with this)).
- James.sutherland.oracle.com 14:38, 23 June 2010 (UTC)
- Began moving content from old ELUG -- introductory material on 1:1 and 1:M mappings.
--Rick 11:51, 24 June 2010 (UTC)
___
-- Ben Gelernter 5/03/11
- ELUG ref
- I removed these references to ELUG. Return here to see if this information needs to be brought forward into this doc.
- The last sentence in the note after the graphic was:
- See Configuring Container Policy for details.
- The last sentence in the note after the graphic was:
- The "fetch" row in the table included the following. The ref to ELUG was removed:
- For more information, see What You May Need to Know About EclipseLink JPA Lazy Loading
- The "fetch" row in the table included the following. The ref to ELUG was removed:
- The very last two sentences in the section were:
- For more information on EclipseLink direct mappings and relationship mappings, see Relational Mapping Types.
- The very last two sentences in the section were:
- For more information on EclipseLink one-to-one mappings, see One-to-Many Mapping, and for information on how to configure these mappings, see Configuring a Relational One-to-Many Mapping.