Open
Conversation
niyazmnazari
approved these changes
Dec 25, 2024
There was a problem hiding this comment.
Thank you for submitting assignment 2. Everything looks correct.
For Promote 3 of Section 1, the correct answer is:
In Type 1, we consider an address field in the customer table. Whenever a customer changes their address, we lose the history of previous changes. To address this, we can create a new table dedicated to storing customer addresses. In this scenario, each time a customer updates their address, the new table allows us to retain the history of all address changes.
Point: 60/70
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? (e.g. Adding or removing code, refactoring existing code, adding reports)
The changes involve creating a new table (product_units), inserting data into it, updating it, and cleaning up old records. This includes:
Dropping and recreating the product_units table.Inserting new rows. Updating the current_quantity with the latest quantity from vendor_inventory. Deleting outdated records for a specified product.
What did you learn from the changes you have made?
How to manage SQL tables and data accurately with complex queries.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Considering dynamic table adjustments without dropping and recreating the table.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Encountered syntax errors and column mismatches, resolved through careful checking and logic adjustments.
How were these changes tested?
Tested by running SQL queries and verifying data integrity and accuracy in the results.
A reference to a related issue in your repository (if applicable)
Checklist