Hi,
That sounds logical but the issue could be that the calling party is simply not
aware that the
called library is using cayenne.
This would mean that an application which is calling some library always should
clear
(and keep) the transaction. This is not very logical.
And what about the ot
Hello Andrus,
I am so sorry you are right Cayenne is generating outer joins. The
problem was that i was checking one of the prefetches for a Many-to-one
relationship where the second query uses an inner join to join the
related table with the root table.
Thank you
Bruno
Em 06-01-2011 09:13,
Which version of Cayenne are you using?
I am checking our unit tests (Cayenne 3.1, but this part hasn't changed from
3.0) including simple to-one and to-many joint prefetching and both generate
outer joins:
SELECT DISTINCT t0.DATE_OF_BIRTH, t0.ARTIST_ID, t0.ARTIST_NAME,
t1.ESTIMATED_PRICE, t1
On Jan 6, 2011, at 10:48 AM, Hans Pikkemaat wrote:
> One library calls the other one.
> The first one is using the iterated query to get some data. It will call the
> second
> library to process the data.
IMO this first library (iterator control code) should be the place that does
transaction
Hi,
After some investigation it comes down to two problems
1)
An example.
I have 2 libraries. One library calls the other one.
The first one is using the iterated query to get some data. It will call the
second
library to process the data.
This second library however is not aware of a iterated
