app/index.yaml
author Sverre Rabbelier <sverre@rabbelier.nl>
Tue, 26 May 2009 20:04:59 +0200
branchgae-fetch-limitation-fix
changeset 2315 29fea493cd56
parent 2261 b297ce894852
child 2595 4c00831ef55c
permissions -rw-r--r--
Use key_name instead of link_id Some entities do not have a link_id, but all entities are guaranteed to have a key_name (or an id).

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

# used to determine which proposals will be accepted
- kind: StudentProposal
  properties:
  - name: org
  - name: status
  - name: __key__

# used for the bulk mailing of students
- kind: Student
  properties:
  - name: scope
  - name: __key__

# used for the cron system
- kind: Job
  properties:
  - name: priority_group
  - name: status
  - name: __key__

# 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.