You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 28, 2022. It is now read-only.
Current schema design of full-text search queries is not customizable to support different important uses-cases. Probably the field-level annotation should be replaced with an object-level (say @FullTextQuery) similar to how it is defined in TheGraph schémas. Then it should support
multiple queries with overlapping field (which may span multiple entities)
different languages
Strict/Partial/search-as-you-go queries (only strict node is activated atm)
support sorting by relevance (ts_rank)
All the options above (and more) are supported by Postgres out-of-the-box so we just need to figure out the right format of the schema definition and translate it into appropriate SQL queries
Current schema design of full-text search queries is not customizable to support different important uses-cases. Probably the field-level annotation should be replaced with an object-level (say @FullTextQuery) similar to how it is defined in TheGraph schémas. Then it should support
All the options above (and more) are supported by Postgres out-of-the-box so we just need to figure out the right format of the schema definition and translate it into appropriate SQL queries
Related issue: Joystream/hydra#457
The text was updated successfully, but these errors were encountered: