Closed mitchshepherd closed 1 year ago
MarkLogic 9.0-4 should add a new optic function to parse a SQL where clause so the flora parser will no longer be needed. Refactor as necessary.
Copied issue from koop-provider-marklogic by jkerr5 commented on Nov 22, 2017
MarkLogic 9.0-4 has been released and now supports a SQL where expression as a where clause. We can now do something like
.where(op.sqlCondition("OBJECTID IN (57011, 34484)")) instead of using the flora sql parser.
We may still need to leverage the flora sql parser to implement https://github.com/koopjs/koop-provider-marklogic/issues/11 as that would require handling some custom SQL function.
This may also fix https://github.com/koopjs/koop-provider-marklogic/issues/7 so check once this is complete.
jkerr5 commented on Jan 24, 2018
Reevaluate if we can get rid of the SQL parser given the current handling of SQL where clauses in the optic API jkerr5 commented 3 days ago
I don't believe this is possible yet per a conversation we recently had. op.sqlCondition does help out, but it can't handle everything yet, such as "TO_DATE".
op.sqlCondition
MarkLogic 9.0-4 should add a new optic function to parse a SQL where clause so the flora parser will no longer be needed. Refactor as necessary.
Copied issue from koop-provider-marklogic by jkerr5 commented on Nov 22, 2017
MarkLogic 9.0-4 has been released and now supports a SQL where expression as a where clause. We can now do something like
.where(op.sqlCondition("OBJECTID IN (57011, 34484)")) instead of using the flora sql parser.
We may still need to leverage the flora sql parser to implement https://github.com/koopjs/koop-provider-marklogic/issues/11 as that would require handling some custom SQL function.
This may also fix https://github.com/koopjs/koop-provider-marklogic/issues/7 so check once this is complete.
jkerr5 commented on Jan 24, 2018
Reevaluate if we can get rid of the SQL parser given the current handling of SQL where clauses in the optic API jkerr5 commented 3 days ago