Open
Conversation
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)
I created the ERDs for the book store, updated the Assignment 2 markdown to include my answer to the question, and updated assignment2.sql to include the completed responses to the questions.
What did you learn from the changes you have made?
I improved my skills in making ERDs and applied the SQL lessons to the answer the questions.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
The last question of Section 3 proved really hard for me and I considered accounting for the nulls through a separate UPDATE STATEMENT altogether, but I adhered to the parameters and figured out how to use coalesce instead.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
As mentioned above, I had a really hard time with the last question. The issue was primarily that when I was writing the subquery as part of the UPDATE statement, coalesce would not remove nulls for the cases in which the WHERE statement didn't apply. I ended up creating a CTE that supplied the recently quantity AND THEN I used coalesce on the CTE as part of the UPDATE statement.
How were these changes tested?
Once the question were completed, I ran the code one question at a time against the original db to ensure that it worked.
A reference to a related issue in your repository (if applicable)
I apologize about the long pull request, my assigment_two branch was forked from the main, so when I committed all changes and then pushed to github, it included the changes made as part of assignment_one.
Checklist