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/Common Relationship Configurations/JoinFetch"
m |
m |
||
Line 10: | Line 10: | ||
-- [[User:ben.gelernter.oracle.com|Ben Gelernter]] 4/28/11 | -- [[User:ben.gelernter.oracle.com|Ben Gelernter]] 4/28/11 | ||
− | : ELUG | + | : ELUG refs |
: I removed these references to ELUG. Return here to see if this information needs to be brought forward into this doc. | : I removed these references to ELUG. Return here to see if this information needs to be brought forward into this doc. | ||
::A couple of the annotations under "How to Use the @JoinFetch Annotation" were to ELUG. I left the annotations in the list but removed the link: | ::A couple of the annotations under "How to Use the @JoinFetch Annotation" were to ELUG. I left the annotations in the list but removed the link: | ||
Line 22: | Line 22: | ||
::Alternatively, you can use batch reading, especially for collection relationships. For more information, see [[Using%20Basic%20Query%20API%20(ELUG)#Using_Batch_Reading|Using Batch Reading]]. | ::Alternatively, you can use batch reading, especially for collection relationships. For more information, see [[Using%20Basic%20Query%20API%20(ELUG)#Using_Batch_Reading|Using Batch Reading]]. | ||
+ | |||
+ | : In the "@JoinFetch Annotation Attributes" table, I remove these links, which were the last items in the Description column for "value": | ||
+ | |||
+ | ::For more information, see the following: | ||
+ | ::* [[Introduction%20to%20EclipseLink%20Expressions%20(ELUG)#What You May Need to Know About Joins|What You May Need to Know About Joins]] | ||
+ | ::* [[Using%20Basic%20Query%20API%20(ELUG)#Using Join Reading with ObjectLevelReadQuery|Using Join Reading with ObjectLevelReadQuery]] | ||
+ | ::* [[Configuring%20a%20Relational%20Mapping%20(ELUG)#Configuring Joining at the Mapping Level|Configuring Joining at the Mapping Level]] |
Revision as of 10:49, 28 April 2011
Why is this talking about fetch groups? Fetch type has nothing to do with fetch groups, it configures LAZY or EAGER (indirection).
- James.sutherland.oracle.com 19:52, 16 June 2010 (UTC)
- Replaced with info for @JoinFetch Annotation
--Rick 14:05, 21 June 2010 (UTC)
- Nope, fetch type is not JoinFetch either, and the default for fetch type is not eager.
- See, Lazy Fetching
- James.sutherland.oracle.com 14:52, 22 June 2010 (UTC)
---
-- Ben Gelernter 4/28/11
- ELUG refs
- I removed these references to ELUG. Return here to see if this information needs to be brought forward into this doc.
- A couple of the annotations under "How to Use the @JoinFetch Annotation" were to ELUG. I left the annotations in the list but removed the link:
- @OneToOne
- @ManyToOne
- A couple of the annotations under "How to Use the @JoinFetch Annotation" were to ELUG. I left the annotations in the list but removed the link:
- I also removed this reference to ELUG. I left in the note, but removed the link:
- Nnote: We recommend setting join fetching at the query level, as not all queries require joining. For more information, see Using Join Reading with ObjectLevelReadQuery.
- Immediately following the above was this item. Again, I left the comment but removed the xref:
- Alternatively, you can use batch reading, especially for collection relationships. For more information, see Using Batch Reading.
- In the "@JoinFetch Annotation Attributes" table, I remove these links, which were the last items in the Description column for "value":
- For more information, see the following: