Skip to content
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

Closed
0x777 opened this issue Nov 21, 2018 · 8 comments
Closed

support all operators on all types #1082

0x777 opened this issue Nov 21, 2018 · 8 comments
Assignees
Labels
a/api/graphql c/server Related to server e/hard Will take weeks of effort k/enhancement New feature or improve an existing feature k/v3-alpha To be supported in DDN Alpha p/high candidate for being included in the upcoming sprint t/native-dbs

Comments

@0x777
Copy link
Member

0x777 commented Nov 21, 2018

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.

@0x777 0x777 added k/enhancement New feature or improve an existing feature c/server Related to server p/high candidate for being included in the upcoming sprint e/hard Will take weeks of effort labels Nov 21, 2018
@0x777
Copy link
Member Author

0x777 commented Nov 21, 2018

Related #625, #1079

@pronevich
Copy link

Is it going some progress on this issue? Just want to know, because of the need to use ltree module

@0x777
Copy link
Member Author

0x777 commented Mar 5, 2019

@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?

@litchfield
Copy link

@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

@roycastro
Copy link

@0x777 is ltree support being actively developed? Can you give some feedback at this point?
By the way, great job with Hasura!!!

@tirumaraiselvan
Copy link
Contributor

@pronevich @litchfield @roycastro Will appreciate using #625 for discussing ltree specific support.

@magick93
Copy link

magick93 commented Apr 1, 2022

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?

@soupi soupi added k/v3-alpha To be supported in DDN Alpha and removed v2 labels Jan 5, 2024
@soupi
Copy link
Contributor

soupi commented Jan 5, 2024

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.

@soupi soupi closed this as completed Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/api/graphql c/server Related to server e/hard Will take weeks of effort k/enhancement New feature or improve an existing feature k/v3-alpha To be supported in DDN Alpha p/high candidate for being included in the upcoming sprint t/native-dbs
Projects
None yet
Development

No branches or pull requests

10 participants