Open
Conversation
final for homework_4.sql
homework 5 finished
reflected for homework 6
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)
Focused on techniques as COALESCE, window functions, string manipulations, and UNION queries, expanding the database with new tables and inserting, deleting, and updating data.
What did you learn from the changes you have made?
How to handle complex SQL queries and database modifications effectively. I gained insights into advanced SQL functions, such as COALESCE and window functions, and understood their practical application.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
For the ethical and equity considerations, I also thought about incorporating automated checks for potential biases in data analysis.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
One challenge was dealing with NULL values in the product table while using the COALESCE function. Understanding how to replace NULL values without affecting non-NULL entries required careful handling.
How were these changes tested?
These changes were tested by executing the SQL queries on the farmersmarket.db and verifying the results against expected outcomes.
A reference to a related issue in your repository (if applicable)
Checklist