Mailing-List: contact gora-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: gora-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of enis.soz@gmail.com designates
 209.85.214.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=lmI5XdTIoGyElWlXGeN7YtsZtyEbM0AhyhpEvqEu+YEu791zh+GUB/gSjvhFV9kHzi
         uI0XyplaGy1Oi3nHB/yYtg6VMkWIDhJ6zTfvQzfLcedaVVVSzzx4LvBoldwzb++lxQVU
         UboKDsi0tCEtLbEKq9zkR9iHYRmFYfZ/i5bu8=
MIME-Version: 1.0
In-Reply-To: <4CC5902F.9000701@mysema.com>
References: <4CC5902F.9000701@mysema.com>
From: =?UTF-8?Q?Enis_S=C3=B6ztutar?= <enis.soz@gmail.com>
Date: Wed, 27 Oct 2010 11:50:55 +0300
Message-ID: <AANLkTimm4ruAeVAfgPcQhj97SBfWkkB5d6oCr_0+KTRJ@mail.gmail.com>
Subject: Re: Type-safe queries for Gora?
To: gora-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016e6ddab7f050c3f04939554d8

--0016e6ddab7f050c3f04939554d8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

Querydsl seems nice indeed. I too dislike dealing with string queries. We
will be glad to collaborate on this. However, there is no string query
support yet at Gora. The Query interface is completely programmatic. Do you
propose to wrap current code with querydsl API ?

Enis

On Mon, Oct 25, 2010 at 5:11 PM, Timo Westk=C3=A4mper <timo.westkamper@myse=
ma.com
> wrote:

> Hello everybody.
>
> I am the maintainer of Querydsl, a typesafe query language for Java.
> Querydsl supports backends like JPA, JDO, SQL, Lucene and Mongodb and we
> would like to know if you guys would like to collaborate on bringing
> type-safe query support to Gora.
>
> The benefits of using Querydsl in comparison to string based queries are
>
>   * code completion in IDE
>   * almost no syntactically invalid queries allowed (type-safe on all
>     levels)
>   * domain types and properties can be referenced safely (no Strings
>     involved!)
>   * adopts better to refactoring changes in domain types
>   * incremental Query definition is easier
>
> The homepage of Querydsl provides basic information on our project :
> http://source.mysema.com/display/querydsl/Querydsl
>
> Querydsl uses APT processors to scan for annotated domain types and
> generates a Query model based on the annotated sources. The query model c=
an
> then be used to construct queries.
>
> Here is an example for JPA
>
> QCustomer customer =3D QCustomer.customer; // query model type
> JPQLQuery query =3Dnew  HibernateQuery (session); // query instance
> Customer bob =3D query.from(customer)
>  .where(customer.firstName.eq("Bob"))
>  .uniqueResult(customer);
>
>
> What do you think?
>
> Best regards,
> Timo Westk=C3=A4mper
>
>

--0016e6ddab7f050c3f04939554d8--