-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Better support for Postgres Arrays #1767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…in parsing the type as ColumnType
|
Review app for commit afae0f0 deployed to Heroku: https://hge-ci-pull-1767.herokuapp.com |
|
Deploy preview for hasura-docs ready! Built with commit cb93ebc |
|
Review app for commit cb93ebc deployed to Heroku: https://hge-ci-pull-1767.herokuapp.com |
|
@nizar-m Please add the right merge label. |
|
closing in favour of #2243 |
|
Review app https://hge-ci-pull-1767.herokuapp.com is deleted |
…quests (fix #1767) hasura/graphql-engine-mono#1768 GitOrigin-RevId: 1161540
…quests (fix #1767) hasura/graphql-engine-mono#1768 GitOrigin-RevId: 1161540
<!-- The PR description should answer 2 important questions: --> ### What Adds tests for `case` and `cast` in the full SQL pushdown path. <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 7fc824958bb094059ba2b8b49afc9fe9f9324e49
Description
Allows following types of queries
And the following mutations with array
Affected components
Related Issues
#348
#349
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds