-
Notifications
You must be signed in to change notification settings - Fork 35
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
✨ Generate Primary Keys. #635
Merged
Merged
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
jortel
force-pushed
the
genkeys
branch
2 times, most recently
from
July 9, 2024 21:42
a54ea3e
to
3a8f00a
Compare
jortel
commented
Aug 13, 2024
mansam
reviewed
Aug 14, 2024
mansam
approved these changes
Aug 15, 2024
jortel
force-pushed
the
genkeys
branch
2 times, most recently
from
August 21, 2024 20:55
537f6be
to
18e5c4a
Compare
Signed-off-by: Jeff Ortel <[email protected]>
Signed-off-by: Jeff Ortel <[email protected]>
Signed-off-by: Jeff Ortel <[email protected]>
mansam
approved these changes
Aug 22, 2024
Signed-off-by: Jeff Ortel <[email protected]>
jortel
force-pushed
the
genkeys
branch
2 times, most recently
from
September 6, 2024 15:48
ec1b59a
to
18e5766
Compare
This was referenced Oct 1, 2024
dymurray
pushed a commit
that referenced
this pull request
Oct 11, 2024
Generate primary keys instead of GORM. This fixes the issue of GORM reusing the highest key after the model with that ID is deleted. When the PK is 0, GORM assigns the next (highest) ID. This approach is to assign the ID ahead of time using a pool managed by tackle. --------- Signed-off-by: Jeff Ortel <[email protected]>
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.
Generate primary keys instead of GORM.
This fixes the issue of GORM reusing the highest key after the model with that ID is deleted.
When the PK is 0, GORM assigns the next (highest) ID.
This approach is to assign the ID ahead of time using a pool managed by tackle.