Message from discussion
New DQL Criteria API
Received: by 10.150.204.19 with SMTP id b19mr1256961ybg.28.1243533572255;
Thu, 28 May 2009 10:59:32 -0700 (PDT)
Return-Path: <adam.hutt...@fracturedatlas.org>
Received: from cepheus.geminisbs.net (cepheus.geminisbs.net [206.71.147.202])
by gmr-mx.google.com with ESMTP id 16si42298gxk.1.2009.05.28.10.59.32;
Thu, 28 May 2009 10:59:32 -0700 (PDT)
Received-SPF: pass (google.com: domain of adam.hutt...@fracturedatlas.org designates 206.71.147.202 as permitted sender) client-ip=206.71.147.202;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of adam.hutt...@fracturedatlas.org designates 206.71.147.202 as permitted sender) smtp.mail=adam.hutt...@fracturedatlas.org
Received: from localhost (localhost.localdomain [127.0.0.1])
by cepheus.geminisbs.net (Postfix) with ESMTP id DD9261710005
for <doctrine-dev@googlegroups.com>; Thu, 28 May 2009 13:58:35 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.854
X-Spam-Level:
X-Spam-Status: No, score=-2.854 tagged_above=-10 required=6.6
tests=[ALL_TRUSTED=-1.8, AWL=0.095, BAYES_00=-2.599,
HTML_MESSAGE=0.001, MSGID_MULTIPLE_AT=1.449]
Received: from cepheus.geminisbs.net ([127.0.0.1])
by localhost (cepheus.geminisbs.net [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id T8OMtvLSkjhL for <doctrine-dev@googlegroups.com>;
Thu, 28 May 2009 13:58:35 -0400 (EDT)
Received: from cepheus.geminisbs.net (cepheus.geminisbs.net [206.71.147.202])
by cepheus.geminisbs.net (Postfix) with ESMTP id 857911710004
for <doctrine-dev@googlegroups.com>; Thu, 28 May 2009 13:58:35 -0400 (EDT)
From: "Adam Huttler" <adam.hutt...@fracturedatlas.org>
To: <doctrine-dev@googlegroups.com>
References: <bcb7aa500905281055i672c4e6bkc594e19dd9a9b1a2@mail.gmail.com>
In-Reply-To: <bcb7aa500905281055i672c4e6bkc594e19dd9a9b1a2@mail.gmail.com>
Subject: RE: [doctrine-dev] New DQL Criteria API
Date: Thu, 28 May 2009 13:58:35 -0400 (EDT)
Message-ID: <006601c9dfbe$0d24b6e0$276e24a0$@huttler@fracturedatlas.org>
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0067_01C9DF9C.861316E0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnfvVOHDiO73HPmTG2Dk3NZbuC0NwAAI/9g
Content-Language: en-us
------=_NextPart_000_0067_01C9DF9C.861316E0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Possibility #1 is the most expressive and easiest to read, IMO. I like the=
=20
variant, even though it's more verbose, because it feels a little more=20
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 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 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=C3=A3o Paulo - SP/Brazil
>
> >
------=_NextPart_000_0067_01C9DF9C.861316E0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dutf-8">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 08.00.0681.0=
00">
<TITLE>RE: [doctrine-dev] New DQL Criteria API</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=3D2>Possibility #1 is the most expressive and easiest to read=
, IMO. I like the variant, even though it's more verbose, because it feels =
a little more flexible.<BR>
<BR>
> -----Original Message-----<BR>
> From: doctrine-dev@googlegroups.com [<A HREF=3D"mailto:doctrine-">mail=
to:doctrine-</A><BR>
> dev@googlegroups.com] On Behalf Of Guilherme Blanco<BR>
> Sent: Thursday, May 28, 2009 1:55 PM<BR>
> To: doctrine-dev@googlegroups.com<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<B=
R>
> to talk about DQL changes.<BR>
> String processing is something really weird, and we want to remove,<BR=
>
> since it's extremely error-prone.<BR>
><BR>
> Basically the purpose of this email is about WHERE conditions.<BR>
> We end up with a lot of 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 far:<BR>
> <A HREF=3D"http://pastebin.com/f4f6c2aa0">http://pastebin.com/f4f6c2aa=
0</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 adding too=
<BR>
> much WTF factor inside.<BR>
><BR>
> So, what's your ideas?<BR>
><BR>
><BR>
> Cheers,<BR>
><BR>
> --<BR>
> Guilherme Blanco - Web Developer<BR>
> CBC - Certified Bindows Consultant<BR>
> Cell Phone: +55 (16) 9215-8480<BR>
> MSN: guilhermebla...@hotmail.com<BR>
> URL: <A HREF=3D"http://blog.bisna.com">http://blog.bisna.com</A><BR>
> S=C3=A3o Paulo - SP/Brazil<BR>
><BR>
> ><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
------=_NextPart_000_0067_01C9DF9C.861316E0--
|
