fix: product pkey conflict caused by import.sql #24
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
|
Nice. I like the Before it was using a generated sequence and I replaced them with hardcoded IDs to simplify Exercise 14 e56fc91 . Can you edit the exercise 14 README file so that the instructions say what it said before? e56fc91#diff-ae26915143c5e0794771625dcfae5d075105a5f3870ceb1c7af28f6574313a8e (i.e. to use curl to get the product IDs) |
njlbenn
previously approved these changes
Oct 11, 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.
The Product PanacheEntity use a generated sequence, but manually adding products with hardcoded id in import.sql bypass the sequence increment, causing a conflict when POSTing a product from the swagger.
I managed to finish the course with a workaround, using
nextvaland altering the sequence to keep simple ids (1,2,3..).