<opinion> A long time ago, in a far far far away place, programmers decided to save storage by using a two-digit representation of the year in dates. In retrospect, not a great decision.
I would suggest that you *not *consider tying a required *orderid *to another implementation's *keyid *... something may change in the future that could break the implied contract between two completely different systems that you make. Your choice, of course, but I would not attempt to "optimize" in this way. </opinion> On Tuesday, July 5, 2016 at 7:41:36 PM UTC-4, Jay Kyburz wrote: > > Hey all, > > Today I'm integrating our app into the Steam store and I would like to use > an entity's key.id() as an "orderid" which must be less than a uint64. > > Anybody know what the maximum number an entity's id can be when > automatically generated? > -- This message (and any associated files) may contain VelociKey confidential and/or privileged information. If you are not the intended recipient or authorized to receive this for the intended recipient, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by sending a reply e-mail and delete this message. Thank you for your cooperation. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/b8d3263f-841c-4445-be57-885bc08d012a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
