[appengine-java] Re: Bug in JDO compiled/named query support
If you are able to issue queries against a table that failed app-engine specific metadata validation that's a bug, and we'd definitely appreciate it if you filed it along with some sample code that succeeds after the exception. The expectation that your model classes have only one primary key field is deeply ingrained in our JDO implemenation, so any success you're having is accidental and unlikely to persist from one sdk version to the next. Thanks, Max On Tue, Oct 27, 2009 at 5:16 PM, Larry Cable wrote: > > I am a little bit confused ... and increasingly frustrated by > the many "limitations" of GAE > as a platform for developing serious applications ... > > Both JDO and the DN implementation support multiple primary keys when > using > IdentityType.APPLICATION and specifying an objectIdClass containing > multiple (String) > fields that maps onto the fields of the entity that are appropriately > annotated ... > > This "appears" to work, with the "exception" (intentional pun:) that > when validating the metadata > the PK exception is thrown ... subsequent queries on the table > "appear" to succeed ... > > while the url documentation could be read as "the datastore only > supports a single primary key field" > I personally don't see anywhere therein where it explicity states > this ... > > On Oct 27, 10:49 am, "Max Ross (Google)" > > > > wrote: > > That is intentional, the App Engine datastore only supports a single > primary > > key field so we enforce this restriction in the JDO/JPA implementation as > > well. The limitations are described in detail here: > http://code.google.com/appengine/docs/java/datastore/creatinggettinga... > > > > > > > > On Tue, Oct 27, 2009 at 8:54 AM, Larry Cable > wrote: > > > > > On Oct 27, 1:14 am, datanucleus wrote: > > > > It's a typo in PM proxy. Fixed in DN SVN thx (in DN 2.0, since DN 1.1 > > > > is not developed now). Obviously you could just use a *normal* PM > > > > instead of a proxy PM. > > > > > thanks Andy... > > > > > while I have your attention ... :) actually I think this one > > > belongs to Jason ... > > > > > there is a bug in org.datanucleus.store.appengine.MetaDataValidator in > > > the > > > validatePrimaryKey() method that causes JDO classes > > > with multiple primary keys (and supporting object id class) classes to > > > fail validation on 1st access ... > > > > > thre method throws an exception if there is more than one > > > field in the class annotated as a primary key ...- Hide quoted text - > > > > - Show quoted text - > > > --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: Bug in JDO compiled/named query support
I am a little bit confused ... and increasingly frustrated by the many "limitations" of GAE as a platform for developing serious applications ... Both JDO and the DN implementation support multiple primary keys when using IdentityType.APPLICATION and specifying an objectIdClass containing multiple (String) fields that maps onto the fields of the entity that are appropriately annotated ... This "appears" to work, with the "exception" (intentional pun:) that when validating the metadata the PK exception is thrown ... subsequent queries on the table "appear" to succeed ... while the url documentation could be read as "the datastore only supports a single primary key field" I personally don't see anywhere therein where it explicity states this ... On Oct 27, 10:49 am, "Max Ross (Google)" wrote: > That is intentional, the App Engine datastore only supports a single primary > key field so we enforce this restriction in the JDO/JPA implementation as > well. The limitations are described in detail > here:http://code.google.com/appengine/docs/java/datastore/creatinggettinga... > > > > On Tue, Oct 27, 2009 at 8:54 AM, Larry Cable wrote: > > > On Oct 27, 1:14 am, datanucleus wrote: > > > It's a typo in PM proxy. Fixed in DN SVN thx (in DN 2.0, since DN 1.1 > > > is not developed now). Obviously you could just use a *normal* PM > > > instead of a proxy PM. > > > thanks Andy... > > > while I have your attention ... :) actually I think this one > > belongs to Jason ... > > > there is a bug in org.datanucleus.store.appengine.MetaDataValidator in > > the > > validatePrimaryKey() method that causes JDO classes > > with multiple primary keys (and supporting object id class) classes to > > fail validation on 1st access ... > > > thre method throws an exception if there is more than one > > field in the class annotated as a primary key ...- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: Bug in JDO compiled/named query support
That is intentional, the App Engine datastore only supports a single primary key field so we enforce this restriction in the JDO/JPA implementation as well. The limitations are described in detail here: http://code.google.com/appengine/docs/java/datastore/creatinggettinganddeletingdata.html#Keys On Tue, Oct 27, 2009 at 8:54 AM, Larry Cable wrote: > > > > On Oct 27, 1:14 am, datanucleus wrote: > > It's a typo in PM proxy. Fixed in DN SVN thx (in DN 2.0, since DN 1.1 > > is not developed now). Obviously you could just use a *normal* PM > > instead of a proxy PM. > > thanks Andy... > > while I have your attention ... :) actually I think this one > belongs to Jason ... > > there is a bug in org.datanucleus.store.appengine.MetaDataValidator in > the > validatePrimaryKey() method that causes JDO classes > with multiple primary keys (and supporting object id class) classes to > fail validation on 1st access ... > > thre method throws an exception if there is more than one > field in the class annotated as a primary key ... > > > > > > > --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: Bug in JDO compiled/named query support
On Oct 27, 1:14 am, datanucleus wrote: > It's a typo in PM proxy. Fixed in DN SVN thx (in DN 2.0, since DN 1.1 > is not developed now). Obviously you could just use a *normal* PM > instead of a proxy PM. thanks Andy... while I have your attention ... :) actually I think this one belongs to Jason ... there is a bug in org.datanucleus.store.appengine.MetaDataValidator in the validatePrimaryKey() method that causes JDO classes with multiple primary keys (and supporting object id class) classes to fail validation on 1st access ... thre method throws an exception if there is more than one field in the class annotated as a primary key ... --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: Bug in JDO compiled/named query support
It's a typo in PM proxy. Fixed in DN SVN thx (in DN 2.0, since DN 1.1 is not developed now). Obviously you could just use a *normal* PM instead of a proxy PM. --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---