Sorry, it was 2 years ago. I added wrong :)
James
On Wednesday, February 3, 2010 9:40:27 AM UTC-8, Ftaylor wrote:
>
> There actually seems to be a mistake in the documentation:
>
> > // Give me all Employees with lastName equal to Smith or Jones
> Query query = pm.newQuery(Employee.class,
>
Hey Google,
If that really is a mistake in the documentation that Ftaylor pointed out,
can you take the 5 minutes and update it? That 5 minutes sure would pay
lots of dividends on the other side in terms of saved minutes trying to
figure out why things aren't working.
The documentation is pos
Wow that mistake in the documentation wasted days of my time. Thankyou
datanucleus.
On Feb 3, 5:40 pm, Ftaylor wrote:
> There actually seems to be a mistake in the documentation:
>
> > // Give me all Employees with lastName equal to Smith or Jones
>
> Query query = pm.newQuery(Employee.class,
There actually seems to be a mistake in the documentation:
> // Give me all Employees with lastName equal to Smith or Jones
Query query = pm.newQuery(Employee.class,
":p.contains(lastName)");
query.execute(Arrays.asList("Smith", "Jones"));
Surely it should be
Oy, this is what I get for not running code before posting it. Good looking
out.
On Tue, Feb 2, 2010 at 1:06 AM, datanucleus wrote:
> >query.setFilter("aliases == alias");
>
> That is invalid JDOQL syntax; the spec is the spec and JDOQL uses Java
> syntax.
> If you have a collection field the
> query.setFilter("aliases == alias");
That is invalid JDOQL syntax; the spec is the spec and JDOQL uses Java
syntax.
If you have a collection field then the filter should be
aliases.contains(:alias)
The poster put the colon in front of a field name (wrong), and
declared a parameter as a vari
