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.
Cory McKenzie
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
-Adding 2 ERDs for a hypothetical bookstore database
-Adding code on assignment2.sql for section 2 and 3
-Adding written responses for section 1 and 4 prompts in assignement2.md
What did you learn from the changes you have made?
I learned how to write more complex, multi-step, queries in sql using a variety of commands
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
One thing I found was that for some of the more complicated problems in section 3 I found it easier to
wrap my head around if I made temp tables as intermediate steps so that not everything had to be in one long statement. I'm not sure if this was always the most appropriate or elegant way to do things but it worked for me.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
My challenges mostly came from getting the syntax right for the query I wanted to make. Usually I had a good idea of what steps were needed and just had to find out how to write the code in the correct way. SQL's "natural" language helped to usually get my first guess most of the way there and then some searching online, looking at notes from class, and trial and error helped get the syntax working.
How were these changes tested?
Lots of trial and error and checking query results and temp tables.
A reference to a related issue in your repository (if applicable)
Checklist