Clarify behavior for a repository which may not be able to support the entire query grammar.

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Domain Model
    • None
    • Hide

      throw NotSupported if a functionality in the query is not supported by underlying repository

      Also - remove UPPER(), LOWER()

      Show
      throw NotSupported if a functionality in the query is not supported by underlying repository Also - remove UPPER(), LOWER()

      What are we supposed to do if our repo can't support part of the CMIS-SQL string? (e.g. we don't support a particular predicate, like UPPER(), LOWER() or pieces of ANY.) Do we throw an exception? Return no results? Return best attempt at results (which then may not strictly map)?

            Assignee:
            Ethan Gur-esh (Inactive)
            Reporter:
            Ryan McVeigh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: