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

Full text search added to existing model of GraphQL #9249

Open
NelsonArguera12 opened this issue Nov 24, 2022 · 2 comments
Open

Full text search added to existing model of GraphQL #9249

NelsonArguera12 opened this issue Nov 24, 2022 · 2 comments
Labels
k/enhancement New feature or improve an existing feature t/native-dbs

Comments

@NelsonArguera12
Copy link

NelsonArguera12 commented Nov 24, 2022

Hi, is there a way to add full-text search functions or fuzzy search in the schema that Hasura creates? I know there are custom functions to do that, but I think it will be complicated to me to add another returning response from a different query into the UI

Just another function like the ones existing, _ilike or like but with full-text search capabilities

I've seen other GraphQL engines with this feature already on the schema itself is there a way to do that with PostgreSQL at least

@NelsonArguera12 NelsonArguera12 added the k/enhancement New feature or improve an existing feature label Nov 24, 2022
@dameleney
Copy link
Member

You will be able to leverage native capabilities of a database such as postgres full text search using parameterized queries when they are released. You can find the rfc here, Parameterized Queries RFC. Please review that rfc and let me know if you have any comments or questions.

We can also consider adding something like _ftsearch to the GraphQL schema but I do not know the feasibility or effort involved at this time.

@NelsonArguera12 I assume the items listed below speak to the motivation behind your request. Let me know if anything is incorrect or missing from the list below.

  1. To perform fuzzy text searches on large amounts of data in a way that leverages the best mechanism to do so supported natively by the database, in this case postgres.
  2. Reduce, time, effort and complexity by not requiring any special set up using views, stored procedures, etc....
  3. As a frontend developers you do not always have DDL privileges to create functions, views, and stored procedures and as a result rely on the data engineering team to make or approve these changes.

@NelsonArguera12
Copy link
Author

@dameleney all of them are on point

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k/enhancement New feature or improve an existing feature t/native-dbs
Projects
None yet
Development

No branches or pull requests

4 participants