Introduce dynamic scope_path regexps Instead of relying on scope_path's being "one slash deep", we should instead allow for either: 1. scope_paths that have a pre-defined depth 2. scope_paths that can be arbitrarily deep We achieve 1 by setting an entities scope_logic to another logic module. We then recursively call getScopeDepth until we get to the topmost entity (that is, an unscoped entity). A little different is the solution to 2, since some entities can have an arbitrarily deep scope (such as Documents), we need to have some way of signaling this to getScopePattern. A clean solution is to return None, rather than a number. If None is returned, the SCOPE_PATH_ARG_PATTERN is returned as regexp instead, which will match an arbitrarily deeply nested scope. The solution for 2 requires that we return None somewhere in the scope_logic chain, the most straight forward method to do so is to override getScopeDepth anywhere such a scope is needed and make it return None. A more elegant solution however, is to set the scope_logic to that module in all entities that require it. Patch by: Sverre Rabbelier

     1

indexes:

     2

     3

# AUTOGENERATED

     4

     5

# This index.yaml is automatically updated whenever the dev_appserver

     6

# detects that a new type of query is run.  If you want to manage the

     7

# index.yaml file manually, remove the above marker line (the line

     8

# saying "# AUTOGENERATED").  If you want to manage some indexes

     9

# manually, move them above the marker line.  The index.yaml file is

    10

# automatically uploaded to the admin console when you next deploy

    11

# your application using appcfg.py.

    12

    13

# Unused in query history -- copied from input.

    14

- kind: Work

    15

  properties:

    16

  - name: inheritance_line

    17

  - name: title