Skip to content

Deprecate hasCompositeKey and provide replacements - #1142

Merged
parsonsmatt merged 3 commits into
masterfrom
matt/has-composite-key
Oct 30, 2020
Merged

Deprecate hasCompositeKey and provide replacements#1142
parsonsmatt merged 3 commits into
masterfrom
matt/has-composite-key

Conversation

@parsonsmatt

@parsonsmatt parsonsmatt commented Oct 29, 2020

Copy link
Copy Markdown
Collaborator

Before submitting your PR, check that you've:

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)

Fixes #685

@parsonsmatt parsonsmatt added this to the 2.11 milestone Oct 29, 2020
@parsonsmatt
parsonsmatt merged commit 0b8f9f3 into master Oct 30, 2020
@parsonsmatt
parsonsmatt deleted the matt/has-composite-key branch April 1, 2021 16:55
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.

hasCompositeKey is technically wrong (alternatively: natural key support?)

1 participant