i'm formulating a single composite property which can be finalized at entity creation time and which will hopefully allow me to retrieve hierarchical data in a desired order. i don't think i can do this with multiple properties as they would each require a inequality operation.
also, this property will be user opaque so i think i can get away with just 8 bytes using base 256! On Oct 23, 2:50 pm, Jon McAlister <[EMAIL PROTECTED]> wrote: > One upper bound is 2^64 since we're using 64-bit integers for these > ids. So, twenty digits would do it if you're encoding it using > decimal, or 11 if you use a base64 encoding. Of course, you may find > using multiple distinct properties may be easier to work with than one > composite property like this. > > Jon > > On Oct 23, 2:27 pm, jeremy <[EMAIL PROTECTED]> wrote: > > > in the life time of an app, what's a reasonable upper bound on the > > integer key().id() ? > > > i need to encode the id into a string - i'm trying to figure out how > > many of the 500bytes to dedicate it. > > > inb4 "be more specific than 'in the life time of an app'" :P --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
