-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support all operators on all types #1082
Comments
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 Full support with all the operators supported by GIST indexes 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? |
@pronevich @litchfield @roycastro Will appreciate using #625 for discussing |
Just realized that Hasura doesnt support all pg operators. And there hasnt been any updates to this issue in 2 years. Thats very concerning. Is full support of Postgres no longer a priority? |
This issue is already addressed in the new Hasura V3 ndc-postgres, hence closing this. Please follow the guide here for Alpha access to Hasura V3. |
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
.The text was updated successfully, but these errors were encountered: