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 xenia_khailenka@tut.by
 designates 209.85.218.217 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4724C24F-FDF0-45D0-94E1-2C52AC1483E8@gmail.com>
References: <C33B50AD-B4DF-416E-BFDE-1D990B9B7259@gmail.com>
	 <145A8A5C-8270-497A-9890-69871D144B21@objectstyle.org>
	 <367914A0-1F0C-4EA7-8905-E24FE64549D2@gmail.com>
	 <F1DD28FB-6EF5-485D-BA6D-B2D48BE3757C@objectstyle.org>
	 <4724C24F-FDF0-45D0-94E1-2C52AC1483E8@gmail.com>
Date: Tue, 26 Jan 2010 15:52:07 +0200
Message-ID: <d57508121001260552p79cc9c1dlc3b129e5f8b3d05f@mail.gmail.com>
Subject: Re: EJBQL client-side challenge
From: Khailenko Ksenia <xenia_khailenka@tut.by>
To: dev@cayenne.apache.org
Content-Type: multipart/alternative; boundary=00032555bc1e7d5d2e047e119734

--00032555bc1e7d5d2e047e119734
Content-Type: text/plain; charset=ISO-8859-1

Does the scenario at
org.apache.cayenne.CayenneContextEJBQLTest.testEJBQLSelect() satisfy to the
conditions you are talking about?
Because in such a case we have the DbEntity with name "MT_TABLE1" and the
ObjEntity with name "MtTable1" - they are different, aren't they? This test
successfully passes with query "SELECT a FROM MtTable1 a", and fails on
query "SELECT COUNT(a) FROM MtTable1 a" but not for the reason that you
have, but because there is a problem with the processing scalar results.
 Could you give a more concrete example if I misunderstood the problem?

2010/1/26 Lachlan Deck <lachlan.deck@gmail.com>

> On 26/01/2010, at 6:51 PM, Andrus Adamchik wrote:
>
> > Will need to investigate that. Could be a bug. IIRC we officially
> supported EJBQL on the client.
>
> Sure. Just to be clear, this error only occurs if the DbEntity name differs
> from the ObjEntity name. Similar problems would occur (I imagine) with
> property names.
>
> >
> > Andrus
> >
> > On Jan 26, 2010, at 2:10 AM, Lachlan Deck wrote:
> >
> >> On 25/01/2010, at 6:19 PM, Andrus Adamchik wrote:
> >>
> >>>> I realise that the original reasoning for this was security
> >>>
> >>> This and also a general desire to encapsulate as many server details as
> possible.
> >>>
> >>>> this presents a challenge for utilising EJBQ
> >>>
> >>> EJBQL should work without knowledge of DbEntity. What errors are you
> getting? We may be able to fix by fixing processing pipeline.
> >>
> >> If you use a simple query such as 'SELECT COUNT(a) FROM
> SomeEntityName....' the error returned is that no such Table/View exists.
> >>
> >> with regards,
> >> --
> >>
> >> Lachlan Deck
> >>
> >>
> >>
> >>
> >
>
> with regards,
> --
>
> Lachlan Deck
>
>
>
>


-- 
Regards, Ksenia Khailenko

--00032555bc1e7d5d2e047e119734--