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
Currently, the documentation for JSONB column operators has support for only _contains, _contained_in, _has_key, _has_keys_any and _has_keys_all.
However, in PostgreSQL, we can execute queries using operators such as >, <, =, among others, as illustrated in the example below:
select*from service_item_instances where (custom_data ->>'screen_size')::int>30;
The documented operators might not suffice for operations like >, <, =, and similar comparisons.
The text was updated successfully, but these errors were encountered:
Currently, we don't support this kind of composition over JSONB columns, and doing so would require a significant modification to our GraphQL syntax and schema. There are no plans to make changes to this in Hasura v2. We plan on providing much greater support for JSONB columns with v3, but it won't be in the first batch of functionality.
We suggest you use one of two features to accomplish this.
Computed fields will allow you to transform the JSONB column so that you can work with it.
Native queries let you write your own SQL and then automatically convert it into a GraphQL structure for you.
Description
Currently, the documentation for JSONB column operators has support for only
_contains
,_contained_in
,_has_key
,_has_keys_any
and_has_keys_all
.However, in PostgreSQL, we can execute queries using operators such as >, <, =, among others, as illustrated in the example below:
The documented operators might not suffice for operations like >, <, =, and similar comparisons.
The text was updated successfully, but these errors were encountered: