Uploaded image for project: 'ModeShape'
  1. ModeShape
  2. MODE-834

Path constraints in XPath do not treat SNS indexes correctly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.1.0.Final
    • 2.0.0.Final
    • JCR, Query
    • None
    • Workaround Exists
    • Hide

      It is always possible to specify wildcard characters for each SNS index. For example, instead of an XPath with '/a/b/c[2]' one can use '/a[*]/b[*]/c[2]' as the path constraint. This is similar to the standard approach for getting the same behavior in JCR-SQL and JCR-SQL2, since these languages require an explicit wildcard for the SNS index unless an exact match to a single value is to be applied. Although the wildcard in JCR-SQL and JCR-SQL2 is '%' rather than '*'.

      Show
      It is always possible to specify wildcard characters for each SNS index. For example, instead of an XPath with '/a/b/c [2] ' one can use '/a [*] /b [*] /c [2] ' as the path constraint. This is similar to the standard approach for getting the same behavior in JCR-SQL and JCR-SQL2, since these languages require an explicit wildcard for the SNS index unless an exact match to a single value is to be applied. Although the wildcard in JCR-SQL and JCR-SQL2 is '%' rather than '*'.
    • Low

      Processing is done incorrectly for XPath queries that contain a path constraint that doesn't have explicit SNS indexes in all path segments. For example, the path constraint '/a/b/c' in XPath should not only match '/a/b/c', but also '/a[2]/b[1]/c[4]'. This is currently not the behavior of XPath queries in ModeShape.

        1. MODE-834-fix.patch
          40 kB

              rhauch Randall Hauch (Inactive)
              rhauch Randall Hauch (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: