Feat: implements sql query and creates a new table for the library_users #635
Conversation
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.
This commit introduces the library_users table to the database schema, designed to store core information for registered library users. Each record includes a UUID-based user ID, first and last name, email address, and a bcrypt-hashed password to support secure authentication.
As part of the homework requirements, this update also adds several SQL reporting queries to the resources/queries directory:
A query that returns a count of media items grouped by type.
A query that calculates the total number of pages currently checked out by all guests.
A query that lists all five library guests along with any associated records from the checked_out_items table using a LEFT JOIN.