Open
Conversation
JzfL
reviewed
Dec 28, 2024
There was a problem hiding this comment.
Nicely done, please try work on UPDATE section at your free time
JzfL
reviewed
Dec 28, 2024
There was a problem hiding this comment.
Please have relationship pointers start and end on the same attribute next time, and employee_shift should be a table rather than an attribute
JzfL
approved these changes
Dec 28, 2024
JzfL
left a comment
There was a problem hiding this comment.
Approved and nicely done, please work on the comments at your free time
This file contains hidden or 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
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.
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Created a data model for a book store, ran commands on sql to organize data
What did you learn from the changes you have made?
Windowed Functions, string manipulations, reverse, count, etc.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
N/A
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
I couldn't solve the last problem.
How were these changes tested?
were resolved on SLQ
A reference to a related issue in your repository (if applicable)
N/A
Checklist