Open
Conversation
khsergvl
reviewed
Nov 14, 2025
| SELECT | ||
| b.vendor_name, | ||
| b.product_name, | ||
| 5 * n.n * b.price_per_qty AS hypothetical_revenue |
|
Thank you for submitting assignment 2. |
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 SQL queries, ERD diagrams, and Markdown documentation for Assignment 2.
What did you learn from the changes you have made?
I learned how to design logical data models, extend ERDs with new entities and relationships, and apply SQL commands such as JOINs, INSERT, UPDATE, DELETE, and window functions.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I considered storing shift info directly in EMPLOYEE but created a separate EMPLOYEE_SHIFT_ASSIGNMENT table to maintain normalization and flexibility.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Yes, structuring the UPDATE query with a CTE and COALESCE required several iterations to fix syntax errors. Testing queries in DB Browser helped verify the logic.
How were these changes tested?
I executed all SQL queries in DB Browser and confirmed no errors. Both ERD diagrams were created and validated in draw.io.
A reference to a related issue in your repository (if applicable)
Checklist