Dbms Lab Final Assignment
Uploaded by
shihab.touhid777Dbms Lab Final Assignment
Uploaded by
shihab.touhid777Lab Final Assignment
Course Code: CSE 2302
Course Title: Database Management Lab
Section 02
Summer 2024
Submitted By:
Name: Mirza Mostafa Abrar
ID: 223014084
Department of Computer Science Engineering, ULAB
Submitted To:
Name: Jannatul Ferdous Ruma
Designation: Lecturer
Department of Computer Science Engineering, ULAB
Date of Submission:
10th September 2024
Event management has a crucial role in organizing activities ranging from
concerts, conferences, and exhibitions to sports events and festivals. Managing
event details, bookings, and ticketing manually can be a challenging and error
prone task leading to inefficiencies for both event organizers and attendees. A
robust database-driven system is required to streamline the entire process. This
report focuses on developing an event management system based on a database
that will efficiently store and manage event related data including event names,
organizers, dates, locations, categories, and ticket availability. The system will
provide users with the ability to browse and search for events based on various
criteria such as category, date, and location, while also offering detailed
information about each event. The system will support ticket booking and
cancellation, tracking ticket sales and availability in real time.
ER Diagram:
DATABASE AND TABLES:
QUERIES:
1.
The query searches the Events and Organizers tables for events
where the company name of the organizer is 'Redfox Entertainment'.
It lists the event names for all the events organized by Redfox
Entertainment.
2.
The query filters the Users table to find users who registered after
January 1, 2023. It will return a list of usernames and their
corresponding registration dates for those who meet this
condition.
3.
The query selects the event name attribute from the event table.
Where the event date is 2024-03-15. There was no match on that date
as there were no events on that day.
4.
The query lists the names of events along with their ticket prices, but
only for events where the price per ticket is more than 50. Any event
that has a ticket price of 50 or less will not be included in the result.
5.
The query returns the names of organizers along with their email
addresses, but only for those organizers whose email addresses are
from gmail.
6.
The query returns the user IDs who have purchased more than 1
tickets for any event, along with the corresponding event IDs and
the number of tickets they bought. The condition (quantity > 1)
ensures that only purchases with more than 1 tickets are shown.
7.
The query returns the username and phone number of users
whose phone numbers begin with "017". The % ensures that the
query matches any phone number starting with these digits
regardless of what is after "017".
8.
The query retrieves the event ID and the total number of tickets
sold for each event. The GROUP BY clause ensures that the SUM is
calculated separately for each event id. The result will be a list
where each row represents an event, and it shows the total
number of tickets sold for that event.
9.
This query will return a list of user ids along with the count of
distinct events they have booked, but only for users who have
booked more than one unique event.
10.
This query will return the names of all events that are held at the
'Convention Center, London'.
11.
This query will return a list of event ids along with the total
number of bookings for each event.
12.
This query will return the names and ticket prices of events where
the ticket price is between 20 and 50.
13.
This query will return a list of user ids along with the total number
of bookings for each user, but only for users who have made more
than one booking.
This lab report has been developed to make an event
management system. The schema shows several interrelated
tables designed to handle many aspects of event organization and
user interaction. The tables include Organizers, Categories, Users,
Events, Tickets, Bookings, Payments, and Cancellations, each
serving a specific function within the system. The design ensures
data integrity through the use of primary and foreign keys.
Primary keys uniquely identify records within each table, while
foreign keys maintain referential integrity by linking related data
across different tables. The designed database schema provides a
foundation for managing events, user interactions, and financial
transactions. This schema supports data management and
retrieval, ensuring the system can effectively handle the
complexities of event management and user input.
