Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4E75D017.9000409@maniatis.org>
Date: Sun, 18 Sep 2011 21:03:51 +1000
From: Aristedes Maniatis <ari@maniatis.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: dev@cayenne.apache.org
Subject: Re: Type safe queries & more
References: <4E42DE88-4245-4573-BB24-7AF9649DD6A8@karlmenn.is>
 <C6479E749D884341B03A760750BB4D8E041BC9B6@eex1.hennig.local>
 <4E731879.4080106@maniatis.org>
 <CAMHEFDhuKcoFeY=tAGPyMa-C+Bresm4Bs=whxZZpSKkK+YPZfg@mail.gmail.com>
In-Reply-To: 
 <CAMHEFDhuKcoFeY=tAGPyMa-C+Bresm4Bs=whxZZpSKkK+YPZfg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 16/09/11 8:23 PM, Atli P�ll Hafsteinsson wrote:
> For me a big part of the reason for implementing this is to get rid of
> text based queries as they cannot be verified and therefore error
> prone. Plus you have to know more about the data structure.

It is possible to have both and still create at this clean chained API. This is already possible in Cayenne today (EJBQL style queries compared to regular Cayenne expressions). Other ORMS (like ActiveRecord in Rails [1] ) also support this dual approach, and I've found it quite useful to be able to mix them as the need arises.

Ari


[1] http://guides.rubyonrails.org/active_record_querying.html (Note the ":clients" syntax is as close as Ruby gets to enumerations or keys, given that the entire language is untyped).

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A