Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-2610

QueryFilter used with explicitTables not working with Oracle or MS SQL Server

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: OpenIDM 3.1.0
    • Fix Version/s: OpenIDM 3.1.0
    • Labels:
      None
    • Environment:
      Oracle, MS SQL Server

      Description

      Using Oracle as the OpenIDM repository, perform this query operation:

      GET /openidm/audit/recon?_queryFilter=true

      The response will be:

      {"code":500,"reason":"Internal Server Error","message":"DB reported failure executing query oracle.jdbc.driver.OraclePreparedStatementWrapper@535d401f with params: {_resource=audit/recon, _pagedResultsOffset=0, _sortKeys=[], _queryId=null, _pageSize=2147483647, _queryExpression=null, _queryFilter=true} error code: 933 sqlstate: 42000 message: ORA-00933: SQL command not properly ended\n"}
      

      This is because the logic for queryFilter code against explicitTables (such as the audit_recon table) has a hard-coded reference to LIMIT and OFFSET clauses. These clauses work fine in MySQL and PostgreSQL, but they are invalid in Oracle and SQL Server.

        Attachments

          Activity

            People

            • Assignee:
              chad.kienle chad.kienle
              Reporter:
              jake.feasel Jake Feasel
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: