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.
Difference between revisions of "Talk:EclipseLinkNewAttributeMappings"
(→Discussion) |
(→Discussion) |
||
| Line 12: | Line 12: | ||
Yes, we definitely need another way to handle JoinFetch, we have some other options with that problem as well. | Yes, we definitely need another way to handle JoinFetch, we have some other options with that problem as well. | ||
| − | :[[User:Karen. | + | :[[User:Karen.moore.oracle.com|Karen.moore.oracle.com]] 21:00, 21 July 2008 (EDT) |
Revision as of 21:04, 21 July 2008
Discussion
For the @BasicCollection and @BasicMap the value/key column's table should not show (Employee) as the default. The table is the basic table, and you cannot change it, so should just remove this table setting.
The private-owned is not an option on the mappings, should be removed.
The join-fetch default is not inner, it is no join-fetch. Should either be checkbox disabled (and not show an option unless checked), or show "Default (None)".
- James.sutherland.oracle.com 14:02, 21 July 2008 (EDT)
Good call on private-owned, missed that here.
Yes, we definitely need another way to handle JoinFetch, we have some other options with that problem as well.
- Karen.moore.oracle.com 21:00, 21 July 2008 (EDT)