On Sat, Apr 18, 2009 at 3:21 PM, David Wilson <david.wil...@entertainmentcloud.com> wrote:
> Is this expected behaviour? and thus do i need to always give a > key_name to guarantee order? this creates scaling issues for order > counter (which is probably why its not in order in the backend :) ) Keys are only guaranteed to be unique, not sequential or in order: http://code.google.com/appengine/docs/python/datastore/keysandentitygroups.html#Paths_and_Key_Uniqueness What is wrong with giving your models a timestamp property (with auto_now_add=True), and sorting by that? Dave. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
