The GPH Library Management System uses MySQL as the database management system to store and manage all project-related data securely and efficiently.
The database plays an important role in handling:
student records
teacher records
books data
issued books
renewal requests
fines
notifications
OTP verification
question papers
The database is designed using relational tables with proper primary keys and relationships to maintain data consistency and security.
To store all library records digitally.
To manage user authentication securely.
To track issued and returned books.
To maintain fine and overdue records.
To manage question paper uploads.
To support approval workflows.
To improve data retrieval speed and accuracy.
Stores student information.
id
name
roll_no
password
branch
semester
is_approved
Stores teacher details.
id
staff_id
password
is_approved
Stores all book records.
id
book_name
author
category
quantity
available_books
Stores book request records from students.
id
student_id
book_id
requested_days
expected_return_date
status
Stores issued book details.
id
student_id
book_id
issue_date
due_date
return_date
fine_amount
Stores renewal requests.
id
issued_book_id
requested_extra_days
new_due_date
status
Stores uploaded question papers.
id
teacher_id
subject_name
semester
branch
file_name
status
Stores OTP verification records.
id
user_email
otp
created_at
Stores reminder and alert notifications.
id
user_id
message
created_at
The database tables are interconnected using:
Primary Keys
Foreign Keys
Example:
students.id → borrow_requests.student_id
books.id → issued_books.book_id
teachers.id → question_papers.teacher_id
These relationships help maintain data integrity and improve database efficiency.
Secure data management
Faster data retrieval
Reduced redundancy
Better relationship handling
Easy scalability
Efficient record tracking
ER Diagram