New DQL Criteria API - doctrine-dev

Message from discussion New DQL Criteria API
Received-SPF: pass (google.com: domain of r.borsc...@gmx.net designates 213.165.64.20 as permitted sender) client-ip=213.165.64.20;
Message-Id: <5C7B1B97-2270-4F82-8BCA-7A8382664ECA@gmx.net>
From: Roman Borschel <r.borsc...@gmx.net>
To: doctrine-dev@googlegroups.com
In-Reply-To: <006601c9dfbe$0d24b6e0$276e24a0$@huttler@fracturedatlas.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="Apple-Mail-1--1060796610"
Subject: Re: [doctrine-dev] Re: New DQL Criteria API
Date: Thu, 28 May 2009 20:12:55 +0200
References: <bcb7aa500905281055i672c4e6bkc594e19dd9a9b1a2@mail.gmail.com> <006601c9dfbe$0d24b6e0$276e24a0$@huttler@fracturedatlas.org>

--Apple-Mail-1--1060796610
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I only want to clarify what this discussion is about.

We have the Query class. It accepts full DQL strings. You can always =20
build any DQL query through string concatenation.
The issue with that is just that *conditional* query construction (if =20
parameter A set condition X, if parameter B, set condition B OR C)
is cumbersome using string concatenation.

That is what the QueryBuilder class should be useful for.

And what we're now wondering is what the best and safest way is to =20
construct expressions with the QueryBuilder API.

It does add nothing in terms of functionality. Just a different way to =20
construct queries that is more suitable if the construction is based =20
on conditions.

Regards

Roman

On May 28, 2009, at 7:58 PM, Adam Huttler wrote:

> Possibility #1 is the most expressive and easiest to read, IMO. I =20
> like the variant, even though it's more verbose, because it feels a =20
> little more flexible.
>
> > -----Original Message-----
> > From: doctrine-dev@googlegroups.com [mailto:doctrine-
> > dev@googlegroups.com] On Behalf Of Guilherme Blanco
> > Sent: Thursday, May 28, 2009 1:55 PM
> > To: doctrine-dev@googlegroups.com
> > Subject: [doctrine-dev] New DQL Criteria API
> >
> >
> > Hi guys,
> >
> > We're talking a lot about Doctrine 2.0 and this time I'm coming here
> > to talk about DQL changes.
> > String processing is something really weird, and we want to remove,
> > since it's extremely error-prone.
> >
> > Basically the purpose of this email is about WHERE conditions.
> > We end up with a lot of possibilities, and we want all of you to =20
> give
> > us suggestions about which way we should move to.
> > Here are the possibilities we came so far:
> > http://pastebin.com/f4f6c2aa0
> >
> > If you have any other suggestions, include them here too.
> > We expect to find the simplest way to build a query without adding =20
> too
> > much WTF factor inside.
> >
> > So, what's your ideas?
> >
> >
> > Cheers,
> >
> > --
> > Guilherme Blanco - Web Developer
> > CBC - Certified Bindows Consultant
> > Cell Phone: +55 (16) 9215-8480
> > MSN: guilhermebla...@hotmail.com
> > URL: http://blog.bisna.com
> > S=E3o Paulo - SP/Brazil
> >
> > >
>
>
>
> >


--Apple-Mail-1--1060796610
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webk=
it-line-break: after-white-space; "><div>I only want to clarify what this d=
iscussion is about.</div><div><br></div><div>We have the Query class. It ac=
cepts full DQL strings. You can always build any DQL query through string c=
oncatenation.</div><div>The issue with that is just that *conditional* quer=
y construction (if parameter A set condition X, if parameter B, set conditi=
on B OR C)</div><div>is cumbersome using string concatenation.</div><div><b=
r></div><div>That is what the QueryBuilder class should be useful for.</div=
><div><br></div><div>And what we're now wondering is what the best and safe=
st way is to construct expressions with the QueryBuilder API.</div><div><br=
></div><div>It does add nothing in terms of functionality. Just a different=
 way to construct queries that is more suitable if the construction is base=
d on conditions.</div><div><br></div><div>Regards</div><div><br></div><div>=
Roman</div><br><div><div>On May 28, 2009, at 7:58 PM, Adam Huttler wrote:</=
div><br class=3D"Apple-interchange-newline"><blockquote type=3D"cite"> <div=
> <!-- Converted from text/plain format --><p><font size=3D"2">Possibility =
#1 is the most expressive and easiest to read, IMO. I like the variant, eve=
n though it's more verbose, because it feels a little more flexible.<br> <b=
r> > -----Original Message-----<br> > From: <a href=3D"mailto:doctrine-dev@=
googlegroups.com">doctrine-dev@googlegroups.com</a> [<a href=3D"mailto:doct=
rine-">mailto:doctrine-</a><br> > <a href=3D"mailto:dev@googlegroups.com">d=
ev@googlegroups.com</a>] On Behalf Of Guilherme Blanco<br> > Sent: Thursday=
, May 28, 2009 1:55 PM<br> > To: <a href=3D"mailto:doctrine-dev@googlegroup=
s.com">doctrine-dev@googlegroups.com</a><br> > Subject: [doctrine-dev] New =
DQL Criteria API<br> ><br> ><br> > Hi guys,<br> ><br> > We're talking a lot=
 about Doctrine 2.0 and this time I'm coming here<br> > to talk about DQL c=
hanges.<br> > String processing is something really weird, and we want to r=
emove,<br> > since it's extremely error-prone.<br> ><br> > Basically the pu=
rpose of this email is about WHERE conditions.<br> > We end up with a lot o=
f possibilities, and we want all of you to give<br> > us suggestions about =
which way we should move to.<br> > Here are the possibilities we came so fa=
r:<br> > <a href=3D"http://pastebin.com/f4f6c2aa0">http://pastebin.com/f4f6=
c2aa0</a><br> ><br> > If you have any other suggestions, include them here =
too.<br> > We expect to find the simplest way to build a query without addi=
ng too<br> > much WTF factor inside.<br> ><br> > So, what's your ideas?<br>=
 ><br> ><br> > Cheers,<br> ><br> > --<br> > Guilherme Blanco - Web Develope=
r<br> > CBC - Certified Bindows Consultant<br> > Cell Phone: +55 (16) 9215-=
8480<br> > MSN: <a href=3D"mailto:guilhermebla...@hotmail.com">guilhermebla=
n...@hotmail.com</a><br> > URL: <a href=3D"http://blog.bisna.com">http://blo=
g.bisna.com</a><br> > S=E3o Paulo - SP/Brazil<br> ><br> > ><br> <br> </font=
> </p> <br> <br> </div> <br></blockquote></div><br></body></html>
--Apple-Mail-1--1060796610--