Repository navigation
Conversation
|
This pull request was made to the wrong repository. If you are a participant, please close it and open it in your own fork instead. Refer to the Assignment Submission Guide for detailed instructions. |
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?
I completed Assignment 2: designed a bookstore logical model (with and without employee shifts), answered the Type 1 vs Type 2 slowly changing dimension prompt, wrote the SQL for Sections 2 and 3 in assignment2.sql, and wrote the Section 4 ethics response in Assignment2.md. This branch was created from assignment-one, so the Assignment 1 files also appear in the diff.
What did you learn from the changes you have made?
I learned how to use COALESCE, window functions, string functions, UNION, CROSS JOIN, and INSERT/DELETE/UPDATE, and how to design a model with a date table and slowly changing dimensions.
Was there another approach you were thinking about making?
For the most recent visit query, I considered ROW_NUMBER versus DENSE_RANK. I used DENSE_RANK so multiple purchases on the same market date share the same visit number.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Keeping each query separate and handling tables that already existed when re-running statements. I fixed these by testing queries one at a time.
How were these changes tested?
I ran each query in DB Browser for SQLite and checked row counts and column values.
Checklist