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
By default, Hasura returns bytea values (the type used by Chaingraph for binary data) in the bytea hex format, which is prefixed with \x (which when escaped in JSON responses, looks like \\x). There's an open issue about returning values in other formats, but no movement to make this default configurable (beyond using computed fields and hiding the source field from the public schema): hasura/graphql-engine#3336
Chaingraph v1 stuck with this default, but it would be nice to polish the API in v2 to not require these unexpected prefixes.
The view strategy in #29 might be a perfect solution to this issue. When #29 is implemented, we should hex-encode (encode(VALUE, 'hex')) every bytea value at the view layer such that Hasura exposes the fields as strings.
The text was updated successfully, but these errors were encountered:
By default, Hasura returns
bytea
values (the type used by Chaingraph for binary data) in thebytea
hex format, which is prefixed with\x
(which when escaped in JSON responses, looks like\\x
). There's an open issue about returning values in other formats, but no movement to make this default configurable (beyond using computed fields and hiding the source field from the public schema): hasura/graphql-engine#3336Chaingraph v1 stuck with this default, but it would be nice to polish the API in v2 to not require these unexpected prefixes.
The view strategy in #29 might be a perfect solution to this issue. When #29 is implemented, we should hex-encode (
encode(VALUE, 'hex')
) everybytea
value at the view layer such that Hasura exposes the fields as strings.The text was updated successfully, but these errors were encountered: