So far we've been explicitly supporting types and their operators. This is not a scalable approach, we should instead support all operators from pg_catalog.pg_operator.
Related #625, #1079
Is it going some progress on this issue? Just want to know, because of the need to use ltree module
@pronevich We will pick this up soon. Can you help us by providing a few examples of the necessary operators and how they should be in graphql?
@0x777 Easy win here would be to support ltree type using the existing graphql lt/lte/etc. This would cover the basic operators <, <=, =, >=, >. We're starting a major new project and would love this! Where do we sign for a paid plan? :-)
Full support with all the operators supported by GIST indexes <, <=, =, >=, >, @>, <@, @, ~, ? would be amazing though!
https://www.postgresql.org/docs/current/ltree.html#LTREE-OP-TABLE
@0x777 is ltree support being actively developed? Can you give some feedback at this point?
By the way, great job with Hasura!!!
@pronevich @litchfield @roycastro Will appreciate using #625 for discussing ltree specific support.
Most helpful comment
@0x777 Easy win here would be to support
ltreetype using the existing graphql lt/lte/etc. This would cover the basic operators<, <=, =, >=, >. We're starting a major new project and would love this! Where do we sign for a paid plan? :-)Full support with all the operators supported by GIST indexes
<, <=, =, >=, >, @>, <@, @, ~, ?would be amazing though!https://www.postgresql.org/docs/current/ltree.html#LTREE-OP-TABLE