No, I'm pretty current (I updated here sometime last week). I just
rebuilt and re-ran and still see the same issue. It is dying in
Expression.fromString() -- it bails on the false in "isActive = false"
(or true):
org.apache.cayenne.exp.parser.ParseException: Encountered "false" at
line 1, column 12.
Was expecting one of:
"(" ...
"+" ...
"-" ...
"$" ...
"obj:" ...
"db:" ...
<NULL> ...
<PROPERTY_PATH> ...
"\'" ...
"\"" ...
<INT_LITERAL> ...
<FLOAT_LITERAL> ...
You can see it specifically listed a $ there, which is probably why
"isActive = $value" parsed.
On a different topic, I know there were SVN issues a few days ago. I
just tried to update and see this:
[11:12:08] ~/Projects/Eclipse/Cayenne30> svn update
svn: PROPFIND request failed on '/repos/asf/cayenne/main/trunk'
svn: PROPFIND of '/repos/asf/cayenne/main/trunk': Could not create SSL
connection through proxy server (https://svn.apache.org)
Anyone else encountering an SVN issue right now?
Thanks!
On Wed, Apr 30, 2008 at 11:08 AM, Andrus Adamchik
<andru..bjectstyle.org> wrote:
>
> On Apr 30, 2008, at 5:57 PM, Michael Gentry wrote:
>
>
> > Andrus,
> >
> > I was thinking "someBoolean = true" (or false) would work, but it
> > doesn't. However, it does work if you evaluate the expression:
> >
> > expression = Expression.fromString("isActive = $value");
> > parameters = new HashMap<String, Boolean>(1);
> > parameters.put("value", Boolean.TRUE);
> > query = new SelectQuery(TestBool.class,
> > expression.expWithParameters(parameters));
> >
> > That worked just fine for me: WHERE t0.isActive = ? [bind:
> 1->isActive:'true']
> >
> > Shouldn't a normal Expression.fromString() be allowed to specify "=
> > true" or "= false"? Can't we internally convert true/false into
> > Boolean.TRUE/Boolean.FALSE?
> >
>
> IIRC Tore added boolean constant parsing to 3.0 some time ago. I could be
> wrong of course. Are you on 2.0.x?
>
> Andrus
>
This archive was generated by hypermail 2.0.0 : Wed Apr 30 2008 - 11:24:38 EDT