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)
Added my answers to the Homework_4.sql file
What did you learn from the changes you have made?
From the COALESCE question, we learned how to handle and replace NULL values within concatenated strings for cleaner data presentation. The Windowed Functions task taught us to use functions like ROW_NUMBER() to assign sequential numbers to rows within partitions of data, allowing us to track and filter specific records such as the most recent visit. In the String Manipulations exercise, we used functions like SUBSTR() and INSTR() to extract and clean substrings within a column, effectively handling and standardizing inconsistent data entries. Lastly, the UNION query demonstrated how to combine results from multiple queries to display distinct aggregate data, such as the highest and lowest sales days, using CTEs and window functions for clear and precise data analysis.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
I did get a bunch of errors as I was trying to find the correct queries, to overcoming these challenges I needed to do a combination careful testing, and iterative refinement of queries as well as more research to understand the SQL functions better.
How were these changes tested?
I tested this code on DB Browser for SQLite
A reference to a related issue in your repository (if applicable)
Checklist