Manage JSONB fields

[gmlion]

Manage JSONB fields

[Zaid-Ajaj]

Hi @gmlion,

Can you please provide a subset of your schema or your full schema from which the types are generated? If they are generated as optional fields, it means the hasura backend annotated them as such.

In postgres databases, assuming that is what you are working with in hasura, jsonb fields are just strings so it makes sense that they are saved as escaped strings. Since the data of JSONB fields can be of any shape, they are always serialized as strings and you are expected to deserialize them on the client side yourself.

[gmlion]

This is the schema portion about a JSONB field

{
              "name": "customData",
              "description": null,
              "args": [
                {
                  "name": "path",
                  "description": "JSON select path",
                  "type": {
                    "kind": "SCALAR",
                    "name": "String",
                    "ofType": null
                  },
                  "defaultValue": null
                }
              ],
              "type": {
                "kind": "NON_NULL",
                "name": null,
                "ofType": {
                  "kind": "SCALAR",
                  "name": "jsonb",
                  "ofType": null
                }
              },
              "isDeprecated": false,
              "deprecationReason": null
            }

Our issue is that inserting values using Snowflaqe they are inserted as json strings, and stored as such. Using other means, we can insert a string representing a json object and have it stored as such.
For example:

query {
  entity {
    json_data
  }
}

// response

{
  "data": {
    "entity": [
      {
        "json_data": {
          "mean": "not-snowflaqe"
        }
      },
      {
        "json_data": "{\"mean\":\"snowflaqe\"}"
      }
    ]
  }
}