Yes, you should be fine once you build a jar and include it in a
directory where your GAE app can actually see it.
On Dec 18, 4:48 pm, Chang Luo chang@gmail.com wrote:
I am working on on a product on GAE, GWT and Android. It contains a
server component on GAE and 2 clients on GWT and
Is there a way to create a mock Key object, or to create a key object
without actually initializing an app engine enviroment?
I want to unit test some code that depends on a JDO object. In order
to create this JDO object, I need to pass in a Key, which it normally
uses as a reference to another
The datastore stats aren't real time as far as I know. So part of the
discrepancy might be new entities created after the stats were
generated?
On Dec 3, 4:19 am, Toby tobias.ro...@sunnymail.mobi wrote:
Hello,
I just discovered the DataStore statistics. That is a great thing!
I got a
I was just looking at the release notes linked to by the App Engine
Blog post about this and I couldn't find any detail about the Improved
java compatibility stuff. Is there another version of the release
notes with more detail?
The release notes linked to in the blog post were these:
Found a better link for us java types:
http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes
On Dec 3, 10:18 pm, Peter Recore peterrec...@gmail.com wrote:
I was just looking at the release notes linked to by the App Engine
Blog post about this and I couldn't find any detail
I have a TestEntity that has an ArrayList of ChildEntities. I want to
get the Entity from the datastore, update an int field in the child
entity, and then swap the position of the two child entities.
However, as soon as I swap the entities, it appears as though the
updates to the int field are
, 2009 at 10:23 PM, Peter Recore peterrec...@gmail.comwrote:
Here's the stacktrace I get when calling remove on a list containing
child elements of a one to many owned relationship.
java.lang.ClassCastException: java.lang.Long cannot be cast to
java.lang.String
On Wed, Nov 11, 2009 at 10:23 PM, Peter Recore peterrec...@gmail.comwrote:
Here's the stacktrace I get when calling remove on a list containing
child elements of a one to many owned relationship.
java.lang.ClassCastException: java.lang.Long cannot be cast to
java.lang.String
Here's the stacktrace I get when calling remove on a list containing
child elements of a one to many owned relationship.
java.lang.ClassCastException: java.lang.Long cannot be cast to
java.lang.String
at
org.datanucleus.store.appengine.DatastoreFKListStoreSpecialization.removeAt
Not really.
Yeah, I was afraid of the relations part. In the use case I'm
dealing with, there are no relations, but maybe the JDO layer can't
infer that. For now I won't worry about it. If it turns out the
fetches related to these deletes are a bottleneck, I will use the low
level API.
Is there a way to delete an entity without having to fetch it from the
datastore first?
Ideally, there would be a deleteObjectById analogue to getObjectById
on PersistenceManager.
The closest I can think of is using Query.deletePersistentAll() and
specifying a keys only query, but I can't tell
11 matches
Mail list logo
