Ltree contains op #5880
Ltree contains op #5880
Conversation
|
Hi @griffio, is there anything I can do to assist on this work item? |
This PR was to show a more complete implementation, the parts necessary to add this LTREE type and really any new type. Ordinarily, adding a new type is not much of a problem, LTREE shares a few operators with existing types and this makes it more tricky to fit it in. It makes sense to me that LTREE is part of the built in PostgreSql grammar as LTREE is a trusted extension It would be good if you could land your existing PR and take this example that is mostly complete, replacing the code in your existing #5875. Also helps that I can approve another person's PR and get it merged, but not my own. I can help with any questions or look into issues. I will rebase this PR first as it has some conflicts with recent changes - then you can take it @yesitskev I reapplied the changes to make it easier to see. You can make your original PR branch contain the same changes. You can see if it aligns with the features you need for LTREE or more work is needed with operators. |
56a4fc1 to
088d5e9
Compare
Add LTREE type Add LTREE operators
Map LTREE type to driver
088d5e9 to
9734f7d
Compare
Add LTREE for binary ops e.g a || b
9734f7d to
f930341
Compare
Example branch for basic
LTREEsupport contains operator - see #5875https://www.postgresql.org/docs/current/ltree.html
LTREEis a trusted PostgreSql extension and still requiresCREATE EXTENSION LtreeShows type mapping of
LTREEtype and Integration test🔕 Not for merging
CHANGELOG.md's "Unreleased" section has been updated, if applicable.