Skip to content

Make upserts handle unique fields #1233

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.

Sign up for GitHub

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

Jump to bottom
Merged
parsonsmatt merged 7 commits into from
Apr 20, 2021
Merged

Make upserts handle unique fields #1233

parsonsmatt merged 7 commits into from
Apr 20, 2021

Conversation

@dmarticus
Copy link
Contributor

@dmarticus dmarticus commented Apr 20, 2021

Before submitting your PR, check that you've:

  • Documented new APIs with Haddock markup
  • Added @since declarations to the Haddock
  • Ran stylish-haskell on any changed files.
  • Adhered to the code style (see the .editorconfig file for details)

After submitting your PR:

  • [] Update the Changelog.md file with a link to your PR
  • Bumped the version number if there isn't an (unreleased) on the Changelog
  • Check that CI passes (or if it fails, for reasons unrelated to your change, like CI timeouts)

@parsonsmatt parsonsmatt changed the base branch from master to matt/fix-postgres-upsert-where April 20, 2021 19:43
@parsonsmatt parsonsmatt merged commit 362728f into yesodweb:matt/fix-postgres-upsert-where Apr 20, 2021
parsonsmatt added a commit that referenced this pull request Apr 20, 2021
@parsonsmatt @dmarticus
Make upserts handle unique fields (#1233) (#1235)
93f6884 
* Make upserts handle unique fields (#1233)

* trying my bset

* idk maybe this works

* remove logs

* spacing

* Require a Unique on upsertManyWhere

* pave the way for the minor version stuff

* add changelog and cabal bump

Co-authored-by: Dylan Martin <dmarticus@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@dmarticus @parsonsmatt