Comments on: Quercus and App Engine – Reading from the data store.

By: KattyBlackyard

KattyBlackyard — Mon, 15 Jun 2009 04:35:59 +0000

Hi, interest post. I’ll write you later about few questions!

By: JaneRadriges

JaneRadriges — Sun, 14 Jun 2009 00:34:07 +0000

The article is ver good. Write please more

By: Herbert Groot Jebbink

Herbert Groot Jebbink — Sun, 24 May 2009 11:36:11 +0000

Hi, see the URL below for an proof of concept how to use SQL CRUD (Create, Retrieve, Update, Delete) in PHP at Google App Engine.

http://sql-to-jdo-for-php-at-gae.appspot.com

By: Herbert Groot Jebbink

Herbert Groot Jebbink — Sat, 23 May 2009 19:38:07 +0000

Hi, I moved to the Quercus from Resin 4.0 and that solved a lot of problems, including the problem here described. However, your method is off course faster when deleting more records. (IMHO a interactive web-apps should never hit that 1000 record limit)

I’m now working on a SQL to JDO wrapper. That way you can use ‘normal’ SQL statements in your PHP apps.

By: derak

derak — Thu, 21 May 2009 04:08:46 +0000

I see what you mean.

As a workaround, you could call:

$q->deletePersistentAll();

The query only has one record loaded and that is the only record that will be deleted.
This worked for me.

Google has a 1000 record limit for queries so you’ll need to build that logic into your grid if your expecting more rows than that. See this link for more info on quotas and limits..

For update, call the set method you defined in the java table class.
$results[0]->setId(YOUR_VALUE_HERE);