native support for postgres array types (close #348)

[rakeshkky]

Description

TODO:- [console] support new input types format (json) for functions.

Allows following types of queries

query q {
  bar: foo (where: { a : { _contained_in : [1,2,3,4,5,6,7,8]  }} ) {
    a
  }

  baz: foo (where: { a : { _contains : [1,2,3,4] }} ) {
    a
  } 
}

And the following mutations with array

mutation m {
  insert_foo ( objects: [ {a: [1,3,5,7,9] } ]){
    affected_rows
    returning {
      a 
      id
    }
  }
}

Support _preprend and _append operators in updating array columns

Affected components

• Server
• Tests
• Console

Related Issues

#348
#349

Solution and Design

• PGColType is modified to support postgres types
• PGColValue is modified to parse json values according to new PGColType
• hdb_type_info view is added to hdb_catalog schema to list all types with details
• catalog version bump

Steps to test and verify

Limitations, known bugs & workarounds

[netlify]

Deploy preview for hasura-docs ready!

Built with commit 8d3af1d

https://deploy-preview-2243--hasura-docs.netlify.com

[hasura-bot]

Review app for commit c392da4 deployed to Heroku: https://hge-ci-pull-2243.herokuapp.com
Docker image for server: hasura/graphql-engine:pull2243-c392da48

[hasura-bot]

Review app for commit d80ac18 deployed to Heroku: https://hge-ci-pull-2243.herokuapp.com
Docker image for server: hasura/graphql-engine:pull2243-d80ac185

[hasura-bot]

Review app for commit 0daab14 deployed to Heroku: https://hge-ci-pull-2243.herokuapp.com
Docker image for server: hasura/graphql-engine:pull2243-0daab141

[dsandip]

@jberryman some more context on this https://hasurahq.slack.com/archives/CKFUG6RCH/p1562793618269300

Also, figure out what to do with enums

[cthurston]

Will this patch allow for array relationships to be defined from a uuid[] array field?

The gui allowed me to define a relationship from a uuid[] field to another table, but when I attempted to use the relationship in a query:

    "hint": "No operator matches the given name and argument type(s). You might need to add explicit type casts.",
     "message": "operator does not exist: uuid[] = uuid",

[andrewalex]

Also related (From the permissions side) #2882

[himat]

What is the status of this?

[karibertils]

Looking forward to this one

[maxcan]

Is it safe to assume that this current PR is dead? @marionschleifer, @0x777 any idea if native array support will be on the roadmap soon?

My hasura instances are littered with array sub tables since I prefer the strict type safety that gives me over JSONB fields.

[s-kris]

Looking forward to this

[0x777]

Hey folks, I'm sorry about letting this PR go stale (preserving backwards compatibility with the above changes is very hard). Over the past few weeks, we've been working on some changes to the codebase that'll help us improve the speed at which we can implement new features. As soon as we are done with it, we'll pick up these PRs.

[maxcan]

@0x777 appreciate the update! thanks!

[michael-land]

What is the status of this?

[maxcan]

@coco98 ?

[axhl]

Any updates on where this sits on the roadmap? Lots of folks are excited about it: #348

[michael-land]

what makes it so hard to get merge/implement? it's more than 2 years since the PR created.

[Fi1osof]

2021 year. Still waiting for.

UPD: can do like this:

query  {
  product_stats (
    args:{
      ids: "{id1, id2}"
    }
  ) {
    id
    total
  }
}

[karibertils]

2022 and still waiting

[sassela]

closing this stale PR in favour of the original tracking issue #348