[appengine-java] Re: Why not use integer primary keys?

2009-12-13 Thread Hershiv Haria
Thanks for the feedback guys. I'll try with a long and assign it using integers, hopefully this should work. Hershiv -- 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

[appengine-java] Re: Why not use integer primary keys?

2009-12-12 Thread Hershiv Haria
On Dec 12, 11:32 am, Shawn Brown big.coffee.lo...@gmail.com wrote: Error in meta-data for my.syncdroidserver.Box.boxID: Unsupported primary key type: int http://code.google.com/appengine/docs/java/datastore/creatinggettinga... How long have these restrictions been in place? I have created

Re: [appengine-java] Re: Why not use integer primary keys?

2009-12-12 Thread Jeff Schnitzer
H, some issues surrounding this: * As you've probably figured out, the datastore natively only supports two types of id, Long and String * Only Long will autogenerate * There is no guarantee that autogenerated values will be monotonic or even valued in the low-order 4 bytes. So, if you are

Re: [appengine-java] Re: Why not use integer primary keys?

2009-12-12 Thread Shawn Brown
Well this won't help to use id as an array index but...  * As you've probably figured out, the datastore natively only supports two types of id, Long and String  * Only Long will autogenerate Key will autogenerate too won't it! and from the api: long