We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v3-engine v3-ndc-postgres
v2 was supporting upserts via
mutation upsert_article { insert_article ( objects: [ { id: 1 title: "First Article", content: "Updated article 1 content", published_on: "2018-10-12" } ], on_conflict: { constraint: article_title_key, update_columns: [content] } ) { returning { id title content published_on } } }
this has not been implemented in v3 so far.
derive a dedicated upsert command for all persisted models.
mutation upsert_article { upsertArticle ( objects: [ { id: 1 title: "First Article", content: "Updated article 1 content", published_on: "2018-10-12" } ], update_columns: [content] } ) { returning { id title content published_on } } }
Implement upsert commands via native operations.
The text was updated successfully, but these errors were encountered:
I am checking with the team for an update on upserts for the Postgres connector.
Sorry, something went wrong.
No branches or pull requests
Component
v3-engine
v3-ndc-postgres
Is your proposal related to a problem?
v2 was supporting upserts via
this has not been implemented in v3 so far.
Describe the solution you'd like
derive a dedicated upsert command for all persisted models.
Describe alternatives you've considered
Implement upsert commands via native operations.
The text was updated successfully, but these errors were encountered: