Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Received-SPF: pass (athena.apache.org: domain of johnthuss@gmail.com
 designates 209.85.216.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <C6479E749D884341B03A760750BB4D8E0480073C@eex1.hennig.local>
References: 
 <CAA-upzop6mXXm1wEAB6x7-6YVmWbKk9J2FaQmBfR-mK5u+0mZA@mail.gmail.com>
	<4F21F7B6.1060608@maniatis.org>
	<032F84BE-64D5-4A57-BAE1-AF5305ACFEA1@objectstyle.org>
	<CAA-upzqzUB3V0xgmS6gLYe0RYx2PUp53VhtD5TCDi4ES-cZ=OA@mail.gmail.com>
	<06821908-6D16-4F8E-8FB8-21B170FE7654@objectstyle.org>
	<CAA-upzrHHvWoDRXn7DYKLxcvbxGBHaD+GSOFkNmb6_dhXv7ytw@mail.gmail.com>
	<12C6EB01-FFD9-4F36-84B6-94B608A1D6CF@objectstyle.org>
	<CAA-upzpk=K1=khCkxiig2PjwKrQmk54DftLWw9xu=tZ6cMLzBg@mail.gmail.com>
	<C6479E749D884341B03A760750BB4D8E0480027D@eex1.hennig.local>
	<4F267D30.7020904@maniatis.org>
	<C6479E749D884341B03A760750BB4D8E04800361@eex1.hennig.local>
	<4F268839.9040604@maniatis.org>
	<CAOUwSGvN=6gEBM-SwGbzndU0uGnVjX+xj1Mv9wWjRBbLJ0YpJA@mail.gmail.com>
	<C6479E749D884341B03A760750BB4D8E0480073C@eex1.hennig.local>
Date: Tue, 31 Jan 2012 14:29:55 -0600
Message-ID: 
 <CAOUwSGuPGvMftpEeiJGZ6GHd2EPSw+UpVV6eKL5W3YxbK0n87A@mail.gmail.com>
Subject: Re: SelectQuery + Orderings
From: John Huss <johnthuss@gmail.com>
To: "dev@cayenne.apache.org" <dev@cayenne.apache.org>
Content-Type: multipart/alternative; boundary=20cf3074b586aa7c9604b7d8d842

--20cf3074b586aa7c9604b7d8d842
Content-Type: text/plain; charset=ISO-8859-1

Well, if your code is well designed your artist fetch logic is probably in
the Artist class so the class name isn't needed.  If you are doing
something inside the class you can use a static import to move all the
artist stuff into the namespace and then use it without qualification.

On Tuesday, January 31, 2012, Durchholz, Joachim <
Joachim.Durchholz@hennig-fahrzeugteile.de> wrote:
>> You can also generate a path builder class so you can
>> do the same thing for related objects too.  For example:
>>
>> Artist.NAME.eq("Picasso")  // equals
>> Artist.DATE_OF_BIRTH.lt(now())   // less than
>
> Having to repeat Artist. all over the place is exactly what I'd like to
get rid of.
>
> Hmm...
> ...
> ... I see it's hard to see whether that's actually a problem or not.
> I see myself arguing on matters of principle, which is nice but risks
failure when confronted with reality.
> I also see John arguing with small examples, which is nice but risks
failure when trying to scale to complicated queries.
>
> How about if everybody with an interest in the topic scour their projects
for the nastiest SQL that they have, and present them here?
> We'd have a set of use cases that will really test the various approaches.
>
> Regards
> Jo
>

--20cf3074b586aa7c9604b7d8d842--