Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (nike.apache.org: domain of grobmeier@gmail.com designates
 209.85.216.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <007B1256-8707-448D-8BE6-B40BF1BA54F4@apple.com>
References: 
 <CAPFNckjRCSYXM7+ToYS6kYwgdQypkGPgLW64yOLjv4N91c-aHg@mail.gmail.com>
 <007B1256-8707-448D-8BE6-B40BF1BA54F4@apple.com>
From: Christian Grobmeier <grobmeier@gmail.com>
Date: Sun, 6 Nov 2011 18:37:04 +0100
Message-ID: 
 <CAPFNckjEhKA7gL+Rp2mHkbu13BBA4cLU5OkdTVbfHh9Fs40TJA@mail.gmail.com>
Subject: Re: Selecting relationships without restriction
To: user@cayenne.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Joe,

thanks for letting me know. This would be a killer feature.

Cheers,
Christian


On Sun, Nov 6, 2011 at 5:35 PM, Joseph Senecal <senecal@apple.com> wrote:
> Christian,
>
> There is no way that I know of to specify additional qualifiers to Cayenn=
e's built in relationships. The design is that getPrices should return all =
prices where Price.article field has been set to that article.
>
> What you can do is add your own method getCurrentPrices that returns all =
non-historic prices. This could either explicitly run a query looking for A=
rticle.articleID =3D Price.articleID and Price.historic is false or null. O=
r you can filter though the list of all Prices to select the prices which a=
ren't historic.
>
> The second option has the advantage that it will automatically notice whe=
n new prices are added or old prices are marked as historic.
>
> The first option has the advantage that it doesn't load all prices into m=
emory, but it doesn't return unsaved current prices. And if the result is c=
ached, it doesn't reflect any changes.
>
> Joe
>
> On Nov 6, 2011, at 8:04 AM, Christian Grobmeier wrote:
>
>> Hi all,
>>
>> I have two tables Article and Price.
>> The table Price can containt historic prices which should not be selecte=
d.
>>
>> I do something like that:
>>
>> Expression expression =3D ExpressionFactory.matchExp("prices.historic", =
false);
>> Expression fullExp =3D
>> expression.orExp(ExpressionFactory.matchExp("prices+.historic",
>> null));
>> SelectQuery query =3D new SelectQuery(Module.class, fullExp);
>> List list =3D ctx.performQuery(query);
>>
>> This generates a correct sql like:
>>
>> SELECT DISTINCT t0....*
>> FROM articles t0
>> LEFT JOIN prices t1 ON (t0.id =3D t1.article_id)
>> WHERE (t1.historic =3D false) OR (t1.historic IS NULL)
>>
>> Using that sql works well on my MySQL db directly.
>>
>> When I run Cayenne, my junit test case fails because I when I call
>> getPrices() I get even the historic ones.
>>
>> For example:
>>
>> List list =3D ctx.performQuery(query);
>> Article a =3D (Article)list.get(0);
>> a.getPrices(); // <--- returns historic true/false
>>
>> I had the expectation that the historic prices should not appear here.
>> Do I miss something?
>>
>> Cheers,
>> Christian
>
>


--=20
http://www.grobmeier.de