Hello,
yes, ID's on GAE are troublesome. they are generally increasing
across your entire dataset, but there are exceptions to that rule (so
you can't expect strictly-increasing ID's). I also wonder what
happens if you assign duplicate key_names using the method that
google describes (since any particular request may be serviced by any
running instance pointing at an eventually consistent copy of your
datastore)
I think if you want to introduce the key name concept to the web2py
DAL, you should first look at gluon/contrib/gql.py to see how the DAL
talks to BigTable. then from there perhaps you can make suggestions.
hope that helps a little.
cfh
On Sep 24, 1:24 am, mdmcginn <michael.d.mcgin...@gmail.com> wrote:
> Of course, web2py automatically assigns record IDs, but in GAE, they
> aren't consecutive. That means this code in my view won't work
> reliably in GAE:
> <a href="{{=URL(r=request,f='respond', args=poll.id+1)}}">Next</a>
>
> Here's a suggested solution. How would I implement it in
> web2py?http://groups.google.com/group/google-appengine-python/browse_thread/...
