Skip to content
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

update ndc-spec from 0.1.0-rc.13 to 0.1.0-rc.14 #93

Merged
merged 4 commits into from
Feb 14, 2024

Conversation

soupi
Copy link
Contributor

@soupi soupi commented Feb 5, 2024

No description provided.

@@ -355,6 +369,7 @@ fn get_field_type(column_type: &models::Type, schema: &models::SchemaResponse) -
nullable: matches!(**element_type, models::Type::Nullable { .. }),
})
}
models::Type::Predicate { .. } => todo!(),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about this one.

@soupi soupi changed the title update ndc-spec to 0.1.0.-rc14 update ndc-spec from 0.1.0.-rc13 to 0.1.0.-rc15 Feb 13, 2024
@soupi soupi changed the title update ndc-spec from 0.1.0.-rc13 to 0.1.0.-rc15 update ndc-spec from 0.1.0-rc.13 to 0.1.0-rc.15 Feb 13, 2024
@soupi soupi changed the title update ndc-spec from 0.1.0-rc.13 to 0.1.0-rc.15 update ndc-spec from 0.1.0-rc.13 to 0.1.0-rc.14 Feb 14, 2024
@soupi soupi marked this pull request as ready for review February 14, 2024 09:33
@soupi soupi merged commit 02d26c1 into main Feb 14, 2024
4 checks passed
@SamirTalwar SamirTalwar deleted the gil/update-ndc-spec-rc14 branch February 14, 2024 10:02
github-merge-queue bot pushed a commit to hasura/ndc-postgres that referenced this pull request Feb 14, 2024
- depends on: hasura/ndc-hub#93
- todo: add changelog entry

### What

We are updating connector to support the latest ndc-connector spec
(0.1.0-rc14).
While fixing some breaking changes, such as renaming `where` to
`predicate`, we also support new capabilities:

1. Explaining mutations via the `/mutation/explain` endpoint
2. Supporting filtering using `in` by columns and variables

### How

1. Since a mutation request may contain multiple mutation operations,
the explain response will contain a field named `<operation_name> SQL
Mutation` and a field named `<operation_name> Execution Plan` for each
operation.
2. To filter in column or variable, we need to compare against a
subquery of the shape `(select value from unnest(<column-or-variable>)
as table(value))`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants