Re: [appengine-java] Optimizations with Datastore + JDO

Hi Jeff, After watching some of the I/O sessions on optimization I got the impression that the JDO api (namely PersistenceManager) does not perform batch operations on JDOs containing lists (e.g. ArrayList<>) of child objects. It seemed like the only way to do this is to use the low level api

Re: [appengine-java] Optimizations with Datastore + JDO

You shouldn't see any significant performance difference between the various java datastore APIs during normal operation. The JDO's classpath scanning may have a significant startup cost, but during execution the costs of RPCs and protocol buffer manipulation tend to dominate over any inefficienci

Re: [appengine-java] Optimizations with Datastore + JDO

Thanks Mat, I'll check out Objectify. If any Googlers are reading this, it would be nice to add a section to the docs clearly describing the performance differences between all of the apis (low level api vs jdo vs jpa vs etc.) and maybe even between all of the different languages. As it stands

[appengine-java] Re: Merging older queries with ancestor queries.

I understand that I will not have a delay in the case of using ancestor queries. This is what I mean: (maybe I failed to make it clear). The problem we have is when you create a new entity (without using ancestor queries) and redirect the view to a list of the entities after creation, you may

[appengine-java] Re: Merging older queries with ancestor queries.

I understand that I will not have a delay in the case of using ancestor queries. This is what I mean: (maybe I failed to make it clear). The problem we have is when you create a new entity (without using ancestor queries) and redirect the view to a list of the entities after creation, you may

[appengine-java] Re: Merging older queries with ancestor queries.

You will not have the delay if you query for your data with an ancestor query. This page explains: http://code.google.com/appengine/docs/java/datastore/hr/overview.html "Ancestor queries work because entity groups are a unit of consistency: all operations are applied to the entire group. Ancestor

[appengine-java] Re: Does JDO auto remove indexes that now have unindexed properties?

> I don't know how you would force a write using JDO. JDOHelper.makeDirty(obj, "fieldName); -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscrib

[appengine-java] Re: Change from String to Integer , now can't rid of Zombie instances... what is the right procedure to do so?

If you are getting this exception when running on the GAE/J cloud, have you deleted all your previously-existing ToBuyBean persistent entities? (This would ensure that no ToBuyBean persistent entity exists that has a quantityToAdd already persisted as a string.) On Oct 27, 10:14 pm, Daniel wrote

Re: [appengine-java] Re: Programmatic creation of an application/app-id... is it possible?

Thanks Gal. On 28/10/2011 06:37, Gal Dolber wrote: Yes, you can, using WebDriver. I don't remember if theres any captcha... that would be a problem. Just emulate what you would do manually. Regards On Thu, Oct 27, 2011 at 6:18 PM, Tom Fennelly > wrote: Guys

[appengine-java] Re: Merging older queries with ancestor queries.

Sorry, the title of the post is meant to be written as: Merging older entities with entities that were created into an entity group. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https:/

[appengine-java] Re: Merging older queries with ancestor queries.

Sorry, the title of the post is meant to be written as: Merging older entities with entities that were created into an entity group. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https:/