Merged
Conversation
…ed by Chun-Yuan Chen.
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
2 participants
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)
Two entity-relationship diagrams (.pdf) were completed, followed by SQL queries in a .sql file with my personal comments. In addition, a response to type 1 vs. type 2 slowly changing dimensions was written in a .md file. The queries make use of COALESCE, TRIM, subqueries, etc. to complete some tasks.
What did you learn from the changes you have made?
Through this practice, I learned a lot about writing and running advanced SQL queries and subqueries in SQLite, got a clearer view of the whole process of moving code and files from a local machine to GitHub with Git commands (and it was also a great chance to see how things change in both sides when working with an existing branch created last week), and built up some skills in designing multi-table databases concept using a bookstore case.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I thought about using other SQL tools like MySQL, since there are so many similar ones out there. It might be a good chance to understand this big family and why there are so many SQL-based tools, and what their similarities and differences are.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
One challenge I faced was that SQL subqueries were more difficult than I thought. Even for a simple calculation question, it sometimes seemed like many subqueries needed to solve it. I realized that one way to make this easier is to have a clear mental map of the tables and their variables and relationships really helps when writing queries.
How were these changes tested?
Many times, there can be more than one solution to a question, so whenever possible, I tried different approaches to generate the results and compared them to make sure the origin approach or the one preferred were solid enough.
A reference to a related issue in your repository (if applicable)
None.
Checklist