Conversation
anjali-deshpande-hub
approved these changes
Apr 10, 2026
| DROP TABLE IF EXISTS temp.recent_visit; | ||
| -- Make new temp table to store recent market visit date for each customer | ||
| CREATE TABLE temp.recent_visit AS | ||
| SELECT DISTINCT |
There was a problem hiding this comment.
DISTINCT is not required here.
|
|
||
|
|
||
|
|
||
| DELETE FROM product_units WHERE product_id = 24; |
There was a problem hiding this comment.
Your query correctly filters by product ID condition. The requirement is to delete the older record for the whatever product you added. You can find the oldest record (e.g., using MIN(snapshot_timestamp)) and delete only that row.
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.
SQL - Assignment 2
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Added code for assignment 2.
What did you learn from the changes you have made?
Store intermediary results in temp tables; perform subqueries; alter table by adding additional columns or updating values in a table; perform nested queries to extract insights that involved aggregation, ordering and ranking, etc.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
For some questions, there are multiple approaches that achieve the same. For instance, instead of storing intermediary results into temp tables, some of the queries could be constructed differently but it would also make them a bit tougher to decipher at a later time. So I opted for using temp tables when I could.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
N/A
How were these changes tested?
All queries were tested within SQLite.
A reference to a related issue in your repository (if applicable)
N/A
Checklist