Map: to-many only, and the map will be keyed by the object property
and contain persistent object values: "john" -> Persistent; "mary" ->
Persistent, etc.
Set is also to-many and is needed mainly for completeness. Our
current Lists are just that - ordered Sets.
Andrus
On Aug 17, 2007, at 8:26 AM, Michael Gentry wrote:
OK, since I'm guilty of not having read the JPA specs (What can I say?
I like Classic Cayenne.), how would something like a Set or Map work?
I'm not talking about the underlying implementation details, but from
a user-perspective. Would a Map interface allow you to do something
like get("firstName") to get the "firstName" database column (or is it
the Java attribute?) from that record? Would Set and Map only work on
to-one relationships?
Thanks,
/dev/mrg
On 8/16/07, Andrus Adamchik (JIRA) <[email protected]> wrote:
Support for mapping to-many as Maps and Sets and Collections
------------------------------------------------------------
Key: CAY-848
URL: https://issues.apache.org/cayenne/browse/
CAY-848
Project: Cayenne
Issue Type: New Feature
Components: Cayenne Core Library
Affects Versions: 3.0
Reporter: Andrus Adamchik
Assignee: Andrus Adamchik
Fix For: 3.0
Per JPA spec we should support mapping to-many relationships as
Lists, Collections, Sets and Maps (we currently only do Lists).
Need to add that stuff to Cayenne classic and map to JPA. I see
the following subtasks:
* Support explicit to-many semantics mapping in ObjRelationship
(collection class; map key for Maps)
* In the Modeler allow to specify the choices in ObjRelationship
Inspector
* In class generation template use correct collection type (I
guess for maps the add/remove semantics can be the same as for
lists ... not sure if we need removeFrom(Object key)??)
* Runtime support, including reverse relationships
* Testing
* Bridging JPA mapping
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
