You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2008/03/15 19:13:42 UTC
Re: svn commit: r637443 - in /cayenne/main/trunk/framework/cayenne-jdk1.5-unpublished/src/test: java/org/apache/cayenne/access/ java/org/apache/cayenne/testdo/inherit/auto/ resources/
On Mar 15, 2008, at 7:31 PM, kmenard@apache.org wrote:
> <obj-relationship name="addresses" source="Employee"
> target="Address" db-relationship-path="employeeAddresses"/>
> + <obj-relationship name="homeAddresses" source="Employee"
> target="HomeAddress" db-relationship-path="employeeAddresses"/>
Hmm.... I know for sure I never had such mapping (which explains why
the bug is there to begin with). Still formally the mapping is valid,
so I guess we'd have to handle it.
Andrus
Re: svn commit: r637443 - in
/cayenne/main/trunk/framework/cayenne-jdk1.5-unpublished/src/test:
java/org/apache/cayenne/access/ java/org/apache/cayenne/testdo/inherit/auto/
resources/
Posted by Kevin Menard <km...@servprise.com>.
Heh. I thought it was a little cranky ;-) Even I'm stepping away from the
issue, no need for you to stay up dealing with it.
--
Kevin
On 3/15/08 5:11 PM, "Andrus Adamchik" <an...@objectstyle.org> wrote:
> Oops, sorry. Sent the unfinished draft. Please disregard the email
> below. I should get some sleep :-)
>
> Andrus
>
>
> On Mar 15, 2008, at 11:09 PM, Andrus Adamchik wrote:
>
>> Again, I am not commenting on the substance of the issue
>>
>
Re: svn commit: r637443 - in /cayenne/main/trunk/framework/cayenne-jdk1.5-unpublished/src/test: java/org/apache/cayenne/access/ java/org/apache/cayenne/testdo/inherit/auto/ resources/
Posted by Andrus Adamchik <an...@objectstyle.org>.
Oops, sorry. Sent the unfinished draft. Please disregard the email
below. I should get some sleep :-)
Andrus
On Mar 15, 2008, at 11:09 PM, Andrus Adamchik wrote:
> Again, I am not commenting on the substance of the issue
>
Re: svn commit: r637443 - in /cayenne/main/trunk/framework/cayenne-jdk1.5-unpublished/src/test: java/org/apache/cayenne/access/ java/org/apache/cayenne/testdo/inherit/auto/ resources/
Posted by Andrus Adamchik <an...@objectstyle.org>.
Again, I am not commenting on the substance of the issue
On Mar 15, 2008, at 10:13 PM, Kevin Menard wrote:
> Yeah, the example is a little odd, but combined with runtime
> relationship
> created in CAY-1009 for base types, the situation does come up. A
> fix of
> CAY-1009 may mitigate the need for this. In which case, we could
> either
> explicitly disallow it or come up with a better alternative.
>
> Off-hand, I'm thinking a means of mapped queries that take the
> qualifier
> into account and cast results to the appropriate type. I suppose
> this would
> have more performance implications than just maintaining the list
> locally,
> but it should take care of any data integrity issues without getting
> too
> ugly.
>
>
> On 3/15/08 2:13 PM, "Andrus Adamchik" <an...@objectstyle.org> wrote:
>
>>
>> On Mar 15, 2008, at 7:31 PM, kmenard@apache.org wrote:
>>
>>> <obj-relationship name="addresses" source="Employee"
>>> target="Address" db-relationship-path="employeeAddresses"/>
>>> + <obj-relationship name="homeAddresses" source="Employee"
>>> target="HomeAddress" db-relationship-path="employeeAddresses"/>
>>
>> Hmm.... I know for sure I never had such mapping (which explains why
>> the bug is there to begin with). Still formally the mapping is valid,
>> so I guess we'd have to handle it.
>>
>> Andrus
>>
>
>
Re: svn commit: r637443 - in
/cayenne/main/trunk/framework/cayenne-jdk1.5-unpublished/src/test:
java/org/apache/cayenne/access/ java/org/apache/cayenne/testdo/inherit/auto/
resources/
Posted by Kevin Menard <km...@servprise.com>.
Yeah, the example is a little odd, but combined with runtime relationship
created in CAY-1009 for base types, the situation does come up. A fix of
CAY-1009 may mitigate the need for this. In which case, we could either
explicitly disallow it or come up with a better alternative.
Off-hand, I'm thinking a means of mapped queries that take the qualifier
into account and cast results to the appropriate type. I suppose this would
have more performance implications than just maintaining the list locally,
but it should take care of any data integrity issues without getting too
ugly.
On 3/15/08 2:13 PM, "Andrus Adamchik" <an...@objectstyle.org> wrote:
>
> On Mar 15, 2008, at 7:31 PM, kmenard@apache.org wrote:
>
>> <obj-relationship name="addresses" source="Employee"
>> target="Address" db-relationship-path="employeeAddresses"/>
>> + <obj-relationship name="homeAddresses" source="Employee"
>> target="HomeAddress" db-relationship-path="employeeAddresses"/>
>
> Hmm.... I know for sure I never had such mapping (which explains why
> the bug is there to begin with). Still formally the mapping is valid,
> so I guess we'd have to handle it.
>
> Andrus
>