I think this is a little special ...
if you have 1..n relation to addresses this could make sense, but for a
relation order to positions this would be difficult. The only way cayenne
could provide a generell map is the PK an I don't think that this would be
helpful. All other attributes are nor
*shrug* that's what I've been doing thus far. But I don't think it's so
special... I find myself writing helper methods quite a bit. :)
As you point out, cayenne can't guess the correct key. But as a
developer, you know what things are (should be) unique. I'm not
suggesting that all to-many
?!
-Ursprüngliche Nachricht-
Von: Robert Zeigler [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. Januar 2007 05:14
An: cayenne-user@incubator.apache.org
Betreff: map properties?
Currently (to the best of my knowledge), cayenne always represents a
to-many relationship as a java.util.List
ah, now i get your idea
-Ursprüngliche Nachricht-
Von: Robert Zeigler [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. Januar 2007 10:03
An: cayenne-user@incubator.apache.org
Betreff: Re: AW: map properties?
I probably didn't explain myself very well, apologies. The values in the
map
Does that make sense?
yes
Am I the only one who thinks that would be incredibly useful? :)
I do too ;-)
Is something like this already planned for 3.0?
yes. In fact JPA spec that we are working on supports this type of
mapping. So Cayenne will too.
Cheers,
Andrus
On Jan 16, 2007,
[mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. Januar 2007 05:14
An: cayenne-user@incubator.apache.org
Betreff: map properties?
Currently (to the best of my knowledge), cayenne always represents a
to-many relationship as a java.util.List. However, I was thinking it
would be nifty if cayenne supported
Currently (to the best of my knowledge), cayenne always represents a
to-many relationship as a java.util.List. However, I was thinking it
would be nifty if cayenne supported map-representations of to-many
relationships. For instance, you could model a relationship between
Users and UserPreferences