Added option to create partitioned tables without primary key #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ArdaKaraderi
added
the
needs review
|
Dear Rick, Based on the demand from the community, if you can update this with the latest changes from the repo and extend it to include List & Hash partitions, I would be happy to merge it. |
ArdaKaraderi
requested review from
ArdaKaraderi
and removed request for
denizgolbas
ArdaKaraderi
requested changes
Oct 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Often in datawarehouses there are tables that have no primary key, they rather use a unique constraint on many dimension foreign keys. TO be able to deal with these tables this PR adds the possibility to create partitioned tables without primary key.
The
pkCompositeOneandpkCompositeTwoparameters are nullable but not rearranged in the method due to backwards compatibility.