Open
Conversation
added 2 commits
November 17, 2025 03:06
- SQL: COALESCE, Window Functions, String Manipulations, UNION, Cross Join, DDL Operations - Logical Data Model: Bookstore ERD with employee shifts - Customer address architectures (Type 1/2 SCD) - All sections completed and tested
DwardEE
approved these changes
Nov 25, 2025
DwardEE
left a comment
There was a problem hiding this comment.
Great work!
Beautiful ERD diagrams. Everything looks good, and no changes are needed.
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?
Completed Assignment 2 covering SQL advanced functions and logical data modeling. Includes COALESCE, window functions, string manipulations, UNION, cross joins, DDL operations, and a complete bookstore ERD.
What did you learn from the changes you have made?
Was there another approach you were thinking about making?
Considered using ROW_NUMBER() instead of DENSE_RANK() for visit numbering, but DENSE_RANK() worked only for some reason.
Were there any challenges?
Faced issues with COALESCE in UPDATE statements and transaction_time data type inconsistencies. Resolved through careful subquery construction and data validation.
How were these changes tested?
Each SQL query executed successfully in SQLite.
Checklist