Use offset_linkid instead of offset to scan >1000 entities.
this is a first-cut. It works in all the ways I could make earlier
versions fail. It passes link_id as URL parameters. It also has a new
class LinkCreator which makes the main body of getListContents even easier
to write.
I wasn't sure if link_id's could have non alphanumeric characters; if so, they
need to be URL encoded/decoded.
I also need to go and remove any mention of raw offsets now, because we don't
use them.
I believe I've talked about this approach with a few of you and it sounded
reasonable. Feel free to roll-back/fix/amend/comment-for-me-to-fix. This is
my first big-logic-change to Melange.
Patch by: Dan Bentley
indexes:
# used to list proposal in descending order of their score
- kind: StudentProposal
properties:
- name: org
- name: status
- name: score
direction: desc
# used to list reviews in ascending order of date
- kind: Review
properties:
- name: is_public
- name: scope
- name: created
# used to determine which orgs have more then 0 slots assigned.
- kind: Organization
properties:
- name: scope
- name: status
- name: slots
# used to order accepted orgs
- kind: Organization
properties:
- name: scope
- name: status
- name: name
# used to determine which proposals have a mentor assigned
- kind: StudentProposal
properties:
- name: org
- name: status
- name: mentor
# AUTOGENERATED
# This index.yaml is automatically updated whenever the dev_appserver
# detects that a new type of query is run. If you want to manage the
# index.yaml file manually, remove the above marker line (the line
# saying "# AUTOGENERATED"). If you want to manage some indexes
# manually, move them above the marker line. The index.yaml file is
# automatically uploaded to the admin console when you next deploy
# your application using appcfg.py.