Support multi-field queries in CQL2PgJSON

Description

Business logic modules are starting to need to execute join queries against multiple data sets, but the CQL2PgJSON class currently assumes that all field elements referenced in a query will be in the same jsonb field.

The new mode should:

  • Accept a list of field names (and possibly associated schemas) on instantiation

  • Require that all field elements referenced in queries be unambiguous if schema validation is in use.

  • Require that if schema validation is not in use, all field elements referenced in queries be prefixed with the appropriate jsonb field name.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Jakub Skoczen July 24, 2017 at 12:42 PM

Released as v1.2.0

frances.webb@cornell.edu July 20, 2017 at 7:39 PM

Thanks for the merge, !

shale99 July 20, 2017 at 6:11 PM

appreciated!

Kurt Nordstrom July 20, 2017 at 6:04 PM

Looking at this now.

shale99 July 20, 2017 at 5:53 PM

guys, i need this merged, the weekend is almost upon us (me) and i have a bunch of code to check in that fixes https://folio-org.atlassian.net/browse/UIU-101#icft=UIU-101 and https://folio-org.atlassian.net/browse/UIIT-33#icft=UIIT-33 that i dont want hanging around.. disappointed face

Done

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created July 18, 2017 at 12:33 PM
Updated November 12, 2018 at 2:23 PM
Resolved July 24, 2017 at 12:43 PM
TestRail: Cases
TestRail: Runs

Flag notifications