Skip to content
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.

Please provide more flexible gql querying #25

Open
jsoneaday opened this issue Aug 21, 2021 · 2 comments
Open

Please provide more flexible gql querying #25

jsoneaday opened this issue Aug 21, 2021 · 2 comments

Comments

@jsoneaday
Copy link

Currently all queries are effectively AND queries. We need to have things like OR, Contains, Greater than or Less Than, Starts With, Ends With, Not Equal, Ranges, etc.

This is hard but for some workflows really necessary. Perhaps start with Contains and Greater Than and Less Than?

@hlolli
Copy link
Contributor

hlolli commented Aug 21, 2021

I'm happy to help design individual query, but there's a limitation inherent with OR and NOT_EQ queries which I can't fix. There are good talks and articles describing why this isn't a feature supported in big-data databases and whey they are inherently slow. There should otoh always be a way to query the data in alternative kind of fashion that you get what you are looking for. Ranges are supported (height min height max in blocks query as example), contains is also possible ex. providing list of ids. But each way of querying requires enormous amount of time in design.

In any case, some feature could be missing which we can support from the list of contrains you mentioned. If we find the highest priority queries we need to support, we'll work on support for them one by one, then I think we are on a good track, knowing that still, it's a lot of work making fast queries with huge amount of data (which is getting exponentially bigger these days).

@jsoneaday
Copy link
Author

jsoneaday commented Aug 21, 2021 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants