VISVESVARAYA TECHNOLOGICAL UNIVERSITY

JNANA SANGAMA, BELAGAVI – 590 018

A Mini Project Report on

EVENT MANAGEMENT SYSTEM SYSTEM

Submitted in partial fulfillment of the requirements as a part of the DBMS lab for the V
semester of degree of Bachelor of Engineering in Information Science and Engineering of
Visvesvaraya Technological University, Belagavi

by
Sooraj - 1RN20IS162

Tharun - 1RN20IS175

Under the Guidance of

Faculty Incharge Lab Incharge

Dr. Hema N Dr. R Rajkumar
Assistant Professor Associate Professor
Dept. of ISE, RNSIT Dept. of ISE, RNSIT

Department of Information Science and Engineering

RNS Institute of Technology

Channasandra, Dr. Vishnuvardhan Road, RR Nagar Post,
Bengaluru – 560 098

2022 – 2023
 RNS INSTITUTE OF TECHNOLOGY
Channasandra, [Link] Road, RR Nagar Post,
Bengaluru – 560 098

DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING

CERTIFICATE

This is to certify that the Mini project report entitled EVENT MANAGEMENT SYSTEM
has been successfully completed by SOORAJ bearing USN 1RN20IS162 and THARUN
bearing USN 1RN20IS175, presently V semester student of RNS Institute of Technology in
partial fulfillment of the requirements as a part of the DBMS Laboratory for the award of the
degree Bachelor of Engineering in Information Science and Engineering under
Visvesvaraya Technological University, Belagavi during academic year 2022 – 2023. It is
certified that all corrections/suggestions indicated for Internal Assessment have been
incorporated in the report deposited in the departmental library. The mini project report has
been approved as it satisfies the academic requirements as a part of DBMS Laboratory for the
said degree.

Dr. Hema N Dr. R Rajkumar Dr. Suresh L

Faculty Incharge Lab Incharge Professor and HOD

External Viva

Name of the Examiners Signature with date

1.

2.

i
 DECLARATION

We, SOORAJ [USN: 1RN20IS162] and THARUN [USN: 1RN20IS175], students of V

Semester BE, in Information Science and Engineering, RNS Institute of Technology hereby
declare that the Mini project entitled EVENT MANAGEMENT SYSTEM has been carried
out by us and submitted in partial fulfilment of the requirements for the V Semester degree of
Bachelor of Engineering in Information Science and Engineering of Visvesvaraya
Technological University, Belagavi during the academic year 2022-2023.

Place: Bengaluru

SOORAJ
[1RN20IS162]

THARUN
[1RN20IS175]

ii
 ABSTRACT

The purpose of Online Book Store is to automate the existing manual system by the help of
computerized equipment and full-fledged computer software, fulfilling their requirements, so
that their valuable data/information can be stored for a longer period with easy accessing and
manipulation of the same. The required software and hardware are easily available and easy to
work with.

Online Book Store, as described above, can lead to error free, secure, reliable and fast
management system. It can assist the user to concentrate on their other activities rather to
concentrate on the record keeping. Thus it will help organization in better utilization of
resources. The organization can maintain computerized records without redundant entries.
That means that one need not be distracted by information that is not relevant, while being
able to reach the information.

iii
 ACKNOWLEDGEMENT

The fulfillment and rapture that go with the fruitful finishing of any assignment would be
inadequate without the specifying the people who made it conceivable, whose steady
direction and support delegated the endeavors with success.

We would like to profoundly thank Management of RNS Institute of Technology for

providing such a healthy environment to carry out this project work.

We would like to express our thanks to our Principal Dr. M K Venkatesha for his
support and inspired us towards the attainment of knowledge.

We wish to place on record our words of gratitude to Dr. Suresh L, Professor and
Head of the Department, Information Science and Engineering, for being the enzyme and
master mind behind our Project work.

We would like to express our profound and cordial gratitude to our Laboratory In
charge Dr. R Rajkumar, Associate Professor, Department of Information Science and
Engineering for his valuable guidance, constructive comments and continuous
encouragement throughout the mini project work.

We would like to express our profound and cordial gratitude to our Faculty In charge
Dr. Hema N, Assistant Professor, Department of Information Science and Engineering for
his valuable guidance in preparing Project report.

We would like to thank all other teaching and non-teaching staff of Information
Science & Engineering who have directly or indirectly helped us to carry out the project
work.

And lastly, we would hereby acknowledge and thank our parents who have been a
source of inspiration and also instrumental in carrying out this project work.

SOORJ (1RN20IS162)

THARUN (1RN20IS175)

iv
 TABLE OF CONTENTS
CERTIFICATE i

DECLARATION ii

ABSTRACT iii

ACKNOWLEDGEMENT iv

1. INTRODUCTION 1

2. LITERATURE SURVEY 3

3. SYSTEM REQUIREMENTS 8

4. SYSTEM DESIGN 9

4.1 Description of ER Diagram

4.2 Description of Relational Schema Diagram

5. IMPLEMENTATION 11

5.1 Front-end Development

5.2 Back-end Development

5.3 SQL implementation

5.3.1 Discussion of Code Segment

5.3.2 Procedures and Triggers

6. SNAPSHOTS 20

7. CONCLUSION AND FURTURE ENHANCEMENT 28

7.1 Conclusion

7.2 Future Enhancement

REFERENCES 29

v
 List of Figures

Figure Number Description Page No

2.1 Components of DBMS 7

4.1 ER-Diagram 9

4.2 Schema Digram 10

5.1 Stored Procedure 18

5.2 Trigger 18

6.1 Home Page of Event 20

Management System

6.2 Admin Page of Event 21

Management System

6.3 About Page of Event 21

Management System

6.4 Event List Page of Event 22

Management System

6.5 Feedback Page of Event 22

Management System

6.6 Login Table 23

6.7 User Table 24

6.8 Booking Table 25

6.9 Feedback Table 26

6.10 Payment Table 27

 List of Tables

Table Number Description Page No

6.6.1 Structure of Login Table 23

6.6.2 Structure of User Table 24

6.6.3 Structure of Booking Table 25

6.6.4 Structure of Feedback Table 26

6.6.5 Structure of Payment Table 27

 Event Management System Introduction

INTRODUCTION

1.1 INTRODUCTION TO SQL

The Structured Query Language (SQL) is the language of databases. Al modern relational
databases, including Access, FileMaker Pro, Microsoft SQL serve and Oracle use SQL as
their basic building block. In fact, it's often the only way that you can interact with the
database itself All of the graphical user interfaces that provide data entry and manipulation
functionality are nothing more than SQL translators. They take the actions you perform
graphically and convert them to SQL commands understood by the database.

1.2 SQL IS LIKE ENGLISH

At this point, you might be thinking that you're not a programmer and learning a programming
language is certainly not up your alley. Fortunately, at its core, SQL is a simple language. It
has a limited number of commands, and those commands are very readable and are almost
structured like English sentences.

1.3 INTRODUCING DATABASES

To understand SQL, it's important to have a basic understanding of how databases work. If
you're comfortable with terms like table, relation and query, feel free to flow right ahead! If
not, you may wish to read the article Database Fundamentals before moving on.

Let's look at an example. Suppose you have a simple database designed to keep the inventory
for a convenience store. One of the tables in your database might contain the prices of the
items on your shelves indexed by unique stock numbers that identify each item:

You'd probably give that table a simple name like "Prices."

1.4 PHP BACKGROUND

PHP is server side scripting system
- PHP stands for "PHP: Hypertext Pre-processor"
- Syntax based on Perl, Java, and C
D [Type here]

Dept of ISE, RNSIT 2022-23 Page 1

 Event Management System Introduction

- Very good for creating dynamic content - Powerful, but somewhat risky!

- If you want to focus on one system for dynamic content, this is a good one to choose.

1.5 HISTORY
- Started as a Perl hack in 1994 by RasmusLerdorf (to handle his resume), developed to
PHP/FI
2.0.
- By 1997 up to PHP 3.0 with a new parser engine by ZeevSuraski and AndiGutmans.
- Version 5.2.4 is current version, rewritten by Zend ([Link]) to include a number of
features, such as an object model Current is version 5 PHP is one of the premier examples of
what an open source project can be PHP Scripts Typically file ends in php--this is set by the
web server configuration Separated in files with the tag. PHP commands can make up an
entire file, or can be contained in html--this is a choice....Program lines end in ":" or you get
an error Server recognizes embedded script and executes.

D [Type here]

Dept of ISE, RNSIT 2022-23 Page 2

 Chapter 2

LITERATURE SURVEY
2.1 Traditional File System
In the early days of computing, data management and storage were a very new concept
for organizations. The traditional approach to data handling offered a lot of the
convenience of the manual approach to business processes (e.g. handwritten invoices &
account statements, etc.) as well as the benefits of storing data electronically.

The traditional approach usually consisted of custom-built data processes and

computer information systems tailored for a specific business function. An accounting
department would have their own information system tailored to their needs, where the
sales department would have an entirely separate system for their needs.

Initially, these separate systems were very simple to set up as they mostly mirrored
the business process that departments had been doing for years but allowed them to do
things faster with less work. However, once the systems were in use for so long, they
became very difficult for individual departments to manage and rely on their data
because there was no reliable system in place to enforce data standards or management.

Separate information systems for each business function also led to conflicts of
interest within the company. Departments felt a great deal of ownership for the data that
they collected, processed, and managed which caused many issues among company-
wide collaboration and data sharing.

2.1.1 Pros and Cons of the Traditional Approach

Pros

 Simple

o Matched existing business processes and functions.

o Companies were not as interested in funding complicated information systems

Dept of ISE, RNSIT 2022-23 Page 3

Event Management System Literature Survey

 Initially low-cost

o Systems were designed to be cheap in order to save on cost.

o Early computing was not viewed as beneficial for large funding.

Cons
 Separated ownership

o Business functions had a high sense of data ownership.

o Departments unwilling to share data for fear of minimizing their superiority.

 Unmanaged redundancy

o Multiple instances of the same data appeared throughout various files, systems, and
databases.

o Information updated in one place was not replicated to the other locations.

o Disk space was very expensive, and redundancy had a big impact on storage.

 Data in consistency

o Redundant data stored in various locations was usually never stored the same way.

o Formatting was not centrally managed.

 Lack of data sharing

o Same data stored in multiple locations.

o Caused unnecessary doubling of efforts for processing and managing data.

 High costs in the long run

o Hiring data processors for each department was very expensive, and each position was
typically working on the same thing just for a different area.

o Doubling of work as well as excessive maintenance cost.

Dept of ISE, RNSIT 2022-23 Page 4

Event Management System Literature Survey

2.2 Downfall of Traditional Management System

Conceived in a relatively centralized era when software was deployed in static
environments, legacy database architectures fail to support an increasingly mobile world
where applications are accessed anytime, anywhere.

Today software users want consistent improvements in usability and expect SaaS
vendors to deliver new features and functionalities needed to achieve their business
objectives. However, legacy database technologies fall short. in serving the needs of
todays distributedand cloud environments for the following reasons:

 Inadequate fail over capabilities

 Insufficient provisions during peak demands Latency issues
 Lack of high availability at all times Increasing operational costs
 Inability to meet the demands of global markets

For all of these reasons, traditional databases are unable to deliver results in a rapidly
growing environment where the workload is geographically distributed across
heterogeneous datacenters. Upgrading to a more distributed data model is costly and
complicated and your DBAs can’t just sit back and give up on this situation. Hence, due
to these various reasons, the downfall of the traditional system was inevitable.

2.3 Introduction to the Database Management System

A database management system (DBMS) refers to the technology for creating and
managing databases. Basically, a DBMS is a software tool to organize (create, retrieve,
update and manage) data in a database.

The main aim of a DBMS is to supply a way to store and retrieve database
information that is both convenient and efficient. By data, we mean known facts that can
be recorded and that have embedded meaning. Normally people use software such as
DBASE IV or V, Microsoft ACCESS, or EXCEL to store data in the form of database.
A datum is a unit of Data. Meaningful data combines to form Information. Hence,
information is interpreted data- data provided with [Link] ACCESS is one of the
most common examples of database management software. Database systems are meant
to handle large collection of information Management of data involves both defining
structures for storage of information and

Dept of ISE, RNSIT 2022-23 Page 5

Event Management System Literature Survey

providing mechanisms that can do the manipulation of those stored information.

Moreover, the database system must ensure the safety of the information stored, despite
system crash or attempts at unauthorized access.

2.3.1 Indicative areas for the use of a DBMS

 Airlines: reservations, schedules etc.
 Telecom : calls made, customer details, network usage etc.

 Universities : registration, results, grades, etc.

 Sales: products, purchases, customers etc.
 Banking: all transactions

2.3.2 Advantages of a DBMS-

A Database Management System has many advantages over the traditional file system
used in the earlier days, such as:

 Data independence: Application programs should be as free or independent as

possible from details of data representation and storage. DBMS can supply an
abstract view of the data for insulating application code from such facts.

 Efficient data access: DBMS utilize a mixture of sophisticated concepts and

techniques for storing and retrieving data competently and this feature becomes
important in cases where the data is stored on external storage devices.

 Data integrity and Security : If data is accessed through the DBMS , the DBMS
can enforce integrity constraint on the data

 Data administration: When several users share the data, integrating the
administration of data can offer major improvements. Experienced professionals
understand the nature of the data being managed and can be responsible for
organizing the data representation toreduce redundancy and make the data to
retrieve efficiently

Dept of ISE, RNSIT 2022-23 Page 6

Event Management System Literature Survey

2.3.3 Components of a DBMS

Figure 2.1 Components of DBMS

 Users: Users may be of any kind, such as data base administrators, system developers or
database users.
 Database application: Database application may be epartmental ,Personal, Organizational
and /or Internal
 DBMS: Software that allows users to create and manipulate database access.

 Database: Collection of logical data as a single unit.

Dept of ISE, RNSIT 2022-23 Page 7

 Chapter 3

SYSTEM REQUIREMENTS

The main purpose of this SRS document is to illustrate the requirements of the project Student
information System and is intended to help any organization to maintain and manage its
student’s personal data.

3.1 Hardware Requirements

 Processor: Any Processor above 500 MHz

 RAM: 8.00GB
 Hard Disk: 512GB
 Compact Disk: 700Mb
 Input device Keyboard
 Output device: Laptop Display Screen

3.2 Software Requirements

 Operating System: Windows 10 or higher

 Database: MYSQL
 Tools WampServer3.0 or higher

Dept of ISE, RNSIT 2022-23 Page 8

 Chapter 4

SYSTEM DESIGN

System design is the process of designing the elements of a system such as the architecture,
modules and components, the different interfaces of those components and the data that goes
through that system.

4.1 Entity Relation Diagram

An entity–relationship model (ER model) describes inter-related things of interest in a
specific domain of knowledge. An ER model is composed of entity types (which classify
the things of interest) and specifies relationships that can exist between instances of those
entity types.

In software engineering an ER model is commonly formed to represent things that a

business needs to remember in order to perform business processes. Consequently, the ER
model becomes an abstract data model that defines a data or information structure that can
be implemented in a database, typically a relational database

Figure 4.1 Entity Relational Diagram

Page 9

Dept of ISE, RNSIT 2022-23

 Event Management System Implementation

4.2 Schema Diagram

A schema contains schema objects, which could be tables, columns, data types, store
procedures, relationships, primary keys, foreign keys. A database schema can be
represented in a visual diagram, which shows the database objects and their
relationship with each other.

Figure 4.2 Schema diagram of Event Management System

Dept of ISE, RNSIT 2022-23

 Event Management System Implementation

Chapter 5
IMPLEMENTATION

5.1 HTML5

HTML5 is a markup language used for structuring and presenting content on the World
Wide Web. It is the fifth and current major version of the HTML standard. It was
published in October 2014 by the World Wide Web Consortium (W3C) to improve the
language with support for the latest multimedia, while keeping it both easily readable by
humans and consistently understood by computers and devices such as web browsers,
parsers, etc.HTML5 is intended to subsume not only HTML 4, but also XHTML 1 and
DOM Level 2HTML.

HTML5 includes detailed processing models to encourage more interoperable

implementations; it extends, improves and rationalizes the markup available for
documents, and introduces markup and application programming interfaces (APIs) for
complex web applications. Many new syntactic features are included. To natively
include and handle multimedia and graphical content, the new <video>, <audio> and
<canvas> elements were added, and support for scalable vector graphics (SVG) content
and MathML for mathematical formulas. To enrich the semantic content of documents,
new page structure elements such as<main>, <section>, <article>,<header>,
<footer>, <aside>, <nav> and <figure>, are added. New attributes are introduced, some
elements and attributes have been removed, and others such as <a>, <cite> and<menu>
have been changed, redefined or standardized.

The APIs and Document Object Model (DOM) are now fundamental parts of the
HTML5 specification and HTML5 also better defines the processing for, any invalid
documents.

5.2 PHP
PHP is a servlet-side scripting language designed primarily for web development but
also used as a general-purpose programming language. Originally created by Rasmus
Lerdorf in I994, the PHP reference implementation is now produced by The PHP
Development Team. PHP originally stood for Personal Home Page, but it now stands for

Dept of ISE, RNSIT 2022-23

Page 11
 Event Management System Implementation

the recursive acronym PHP: Hypertext Preprocessor.

PHP code may be embedded into HTML or HTML5 markup, or it can be used in
combination with various web template systems, web content management systems and
web frameworks. PHP code is usually processed by a PHP interpreter implemented as a
module in the webserver

5.3 SQLite (Structured Query Language)

SQLite is an in-process library that implements a self-contained, serverless, zero-

configuration, transactional SQL database engine. The code for SQLite is in the public
domain and is thus free for use for any purpose, commercial or private. SQLite is the
most widely deployed database in the world with more applications than we can count,
including several high-profile projects.

SQLite is an embedded SQL database engine. Unlike most other SQL databases,
SQLite does not have a separate server process. SQLite reads and writes directly to
ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and
views, is contained in a single disk file. The database file format is cross-platform - you
can freely copy a database between 32-bit and 64-bit systems or between big-endian and
little-endian architectures. These features make SQLite a popular choice as an
Application File Format. SQLite database files are a recommended storage format by the
US Library of Congress. Think of SQLite not as a replacement for Oracle but as a
replacement for fopen().

SQLite is a compact library. With all features enabled, the library size can be less
than 750KiB, depending on the target platform and compiler optimization settings. (64-
bit code is larger. And some compiler optimizations such as aggressive function inlining
and loop unrolling can cause the object code to be much larger). There is a tradeoff
between memory usage and speed. SQLite generally runs faster the more memory you
give it. Nevertheless, performance is usually quite good even in low-memory
environments. Depending on how it is used, SQLite can be faster than direct filesystem
I/O.

Dept of ISE, RNSIT 2022-23

 Event Management System Implementation

5.4 Code Snippets

5.4.1 Connectivity to Database
<?php

$server = "localhost";
$user = "root";
$pass = "";
$database = "event_management_system";

$conn = mysqli_connect($server, $user, $pass, $database);

if (!$conn) {
die("<script>alert('Connection Failed.')</script>");
}

?>
5.4.2 Insert a Record in User
<?php
session_start();
error_reporting(0);

include '[Link]';

if (isset($_POST['submit'])) {
$username = $_POST['username'];
$email = $_POST['email'];
$password = ($_POST['password']);
$cpassword = ($_POST['cpassword']);

//$sql1 = "SELECT * FROM login WHERE email='$email' ";

$sql1 = "SELECT `login_id`, `email`, `name`, `user_id`, `password` FROM `login`
WHERE 'email'='$email'";
$result1 = mysqli_query($conn, $sql1);
if (!$result1->num_rows > 0) {
if ($password == $cpassword) {

Dept of ISE, RNSIT 2022-23 Page 13

 Event Management System Implementation

$sql = "SELECT * FROM user WHERE email='$email' AND username = '$username' ";
$result = mysqli_query($conn, $sql);
if ($result->num_rows > 0) {
$row = $result->fetch_row();
//$sql = "INSERT INTO `login`(`login_id`, `email`, `user_id`,
`password`) VALUES (NULL,'$email','$row[0]','$password ')";
$sql = "INSERT INTO `login`(`login_id`, `email`, `name`, `user_id`,
`password`) VALUES (NULL,'$email','$username','$row[0]','$password ')";
$result = mysqli_query($conn, $sql);
if ($result) {
echo "<script>alert('Wow! Admin Registration Completed.')
</script>";
//$username = "";
$email = "";
$_POST['password'] = "";
$_POST['cpassword'] = "";

} else {
echo "<script>alert('Woops! Something Wrong Went.')</script>";
}
} else {
echo "<script>alert('register as a user to become an ADMIN.')</script>";
}

} else {
echo "<script>alert('Password Not Matched.')</script>";
}
}else {
echo "<script>alert('admin alredy exist.')</script>";
}
}

?>
5.4.3 View the contents of User details
<?
php
include '[Link]';
//$query = "SELECT * FROM user " ;
$query = "SELECT `login_id`, `email`, `name`, `user_id` FROM `login` WHERE 1";
$res = mysqli_query($conn,$query);
$all_property = array();

Dept of ISE, RNSIT 2022-23 Page 14

 Event Management System Implementation

while ($property = mysqli_fetch_field($res)) {

echo '<th>' . $property->name . '</th>';
array_push($all_property, $property->name);
}
echo '</thead>';

while ($row = mysqli_fetch_array($res)) {

echo "<tr>";
foreach ($all_property as $item) {
echo '<td>' . $row[$item] . '</td>';
}
echo '</tr>';
}
echo "</table>";

?>

5.4.4 Admin Login

<?php
session_start();
error_reporting(0);

include '[Link]';

if (isset($_POST['submit'])) {
$email = $_POST['email'];
$password = ($_POST['password']);

//$sql = "SELECT * FROM login WHERE email='$email' ";

$sql = "SELECT * FROM login WHERE email='$email' AND password='$password'";
$sql1 = "SELECT * FROM user WHERE email='$email' ";
$result = mysqli_query($conn, $sql);
$result1 = mysqli_query($conn, $sql1);
if ($result1->num_rows > 0) {
if ($result->num_rows > 0) {
$row = mysqli_fetch_assoc($result);
$_SESSION['username'] = $row['username'];

Dept of ISE, RNSIT 2022-23 Page 15

 Event Management System Implementation

} else {
echo "<script>alert('Woops! Email or Password is Wrong.')</script>";
}
}else {
echo "<script>alert('Woops! Email or Password is not admin
registered.')</script>";
}
}

?>

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">

<title>Admin Login Form </title>

<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="[Link]">
<script src="[Link] crossorigin="anonymous"></script>
</head>
<body>

<div class="main">
<div class="container">
<form action="" method="POST" class="login-email">
<p class="login-text" style="font-size: 2rem; font-weight: 800;">Admin
Login only</p><br>
<div class="input-group">
<input type="email" placeholder="admin@[Link]"
name="email" >
</div><br>
<div class="input-group">
<input type="password" placeholder="Password"
name="password" >
</div><br>
<div class="input-group">
<button name="submit"
class="btn">Login</button><br><br><br>

Page 16
Dept of ISE, RNSIT 2022-23
 Event Management System Implementation

</div>
<div class="navbar1">
<ul>
<li style="float:right;"><a
href="[Link]
<li style="border-right: 1px solid #bbb;float:right;"><a
href="[Link]">FEEDBACK</a></li>
<li style="border-right: 1px solid #bbb;float:right;"><a
href="[Link]
<li style="border-right: 1px solid #bbb;float:right;"><a
href="[Link]">ABOUT</a></li>
<li style="border-right: 1px solid #bbb;float:right;"><a
class= "active" href="[Link]
<li style="background-color:#ff7200;padding:20px 25px
20px 20px;">EVENT MANAGEMENT SYSTEM</li>
<i class="fas fa-bars"></i>
</ul>
</div>
</div>
</div>
</div>

</form>
</div>
</body>
</html>

5.5 Stored Procedure

SQLite does not provide the stored procedure concept; basically, stored procedure means
we can prepare a single code, and that code we can reuse again and again as per user
requirement.

A procedure in SQL (often referred to as stored procedure), is a reusable unit that

encapsulates the specific business logic of the application. A SQL procedure is a group of
SQL statements and logic, compiled and stored together to perform a specific task.

Page 17
Dept of ISE, RNSIT 2022-23
 Event Management System Implementation

Figure 5.1 Stored Procedure of Event Management System

5.6 Trigger
The Trigger will add user details to table user.

Figure 5.2 Trigger of Event Management System

Trigger is a statement that a system executes automatically when there is any

modification to the database. In a trigger, we first specify when the trigger is to be executed
and then the actionto be performed when the trigger executes. Triggers are used to specify
certain integrity constraint and referential constraints that cannot be specified using the
constraint mechanism of SQL.

Dept of ISE, RNSIT 2022-23 Page 18

 Event Management System Implementation

Sytnax:

CREATE TRIGGER schema.trigger_name  
ON table_name  AFTER  {INSERT, UPDATE, DELETE}  
[NOT FOR REPLICATION]  
AS  
{SQL_Statements}  

Dept of ISE, RNSIT 2022-23 Page 19

 Chapter 6
SNAPSHOTS

6.1 The Login and Home Page

Figure 6.1 Home Page of Event Management System

Dept of ISE, RNSIT 2022-23 Page 20

 Envent Management System Snapshots

6.2 Admin Login Page

Figure 6.2 Admin login page of Event Management System

6.3 About Page

Figure 6. 3 Classes Page of Student Result Management System

Dept of ISE, RNSIT 2022-23 Page 21

 Envent Management System Snapshots

6.4 Event List Page

Figure. 6.4 Event list page of Event Management System

6.5 Feedback Form Page

Figure 6.5 Feedback Form page of Event Management System

Dept of ISE, RNSIT 2022-23 Page 22

 Envent Management System Snapshots

Dept of ISE, RNSIT 2022-23

 Envent Management System Snapshots

6.6 Table Structure

6.6.1 Login Table

Table Name: Login

Figure 6.6 Login page table

Fieldname Datatype Length Key

Login_id Integer 10 Primary

email Varchar 20

name Varchar 30

User_id Integer 10

password Integer 10

Table 6.1 login page

Table 6.1 shows the login page which has five attributes: login_id, email, name,user_id and password.
Here login_id is a primary key

Dept of ISE, RNSIT 2022-23 Page 23

 Envent Management System Snapshots

6.6.2 User Table

Table Name: User

Figure 6.7 structure the User table

Fieldnam Datatype Length Key

e
User_id Integer 10 Primary
Username Varchar 30
Email Varchar 30
Password Varchar 30

Table 6.2 structure the User table

Table 6.2 shows the structure the User table which has four attributes:
user_id,username,email,password.user_id is a primary key

Dept of ISE, RNSIT 2022-23 Page 24

 Envent Management System Snapshots

6.6.3 Booking Table

Table Name: Booking

Figure 6.8 Structure of Boking table

Fieldname Datatyp Length Key

e
Booking_id Integer 10 Primary
Name Varchar 15
Email Varchar 20
Event_name Varchar 20
City Varchar 10
Venue Varchar 20
Date Date
Phone Varchar 10
Attendees Varchar 15
Time Time
Additional_r Varchar 10
equirement
User_id Integer 10 Reference

Table 6.3 Booking Table

Table 6.3 shows the structure of Booking Table which has twelve attributes:
booking_id,name,email,event_name,city,venue,date,phone,attendess,time,additional_requirem
ent,user_id. Booking_id is primary key here and user_id is reference key from user table.

Dept of ISE, RNSIT 2022-23 Page 25

 Envent Management System Snapshots

6.6.4 Feedback Table

Table Name: Feedback

Figure 6.9 Structure of Feedback table

Fieldname Datatype Length Key

Feedback_ Integer 10 Primary
id
Name Varchar 15
Email Varchar 15
Feedback Varchar 100
User_id Integer 10 Reference

Table 6.4 Feedback table

Table 6.4 shows structure of Feedback table which has six attributes:
feedback_id,name,email,feedback,user_id. Feedback_id is a primary key and user_id is
reference key from user table.

Dept of ISE, RNSIT 2022-23

Page 26
 Envent Management System Snapshots

6.6.5 Payment Table

Table Name: Payment

Figure 6.10 Structure of Payment table

Fieldname Datatype Length Key

Payment_id Integer 1 Primary
0
Name_on_card Varchar 1
0
Card_number Integer 1
2
Exipry_date Date
Cvv Integer
3
User_id Integer Reference
1
0
Table 6.5 payment table.

Table 6.5 shows structure of payment table which has six attributes:
payment_id,name_on_card,card_number,expiry_date,cvv,user_id. Payment_Id is the
primary key and user_id is reference key from user table.

Dept of ISE, RNSIT 2022-23 Page 27

 Chapter 7

CONCLUSION

To conclude the description about the project : The project, developed using PHP and MySQL
is based on the requirement specification of the user and the analysis of the existing system,
with flexibility for future enhancement. The expanded functionality of today’s software
requires an appropriate approach towards software development.
From a proper analysis of positive points and constraints on the project, it can be concluded
that the application makes entire process online. It is highly efficient UI based component
which meets all user requirements

FUTURE ENHANCEMENTS

Our project is a fairly simple Database consisting of a few fields, adding more information and
being able to manage more student information with added functionality. All in all, making it
a more robust system with added functionalities to enhance the overall project features. Fields
like event start time, prizepool, event rules that can be availed can also be Implemented into
the project. Modification options for the registered events by user.

Page 28
Dept of ISE, RNSIT 2022-23
 REFERENCES

[1] [Link]
[2] [Link]
[3] Fundamentals of Database System, Ramez Elmasri and Shamkant [Link], 7th
Edition, 2017, Pearson.
[4] Database Management System, Ramakrishna and Gehrke, 3rd Edition, 2014, McGraw
Hill. The Complete Reference PHP from [Link] and [Link].
[5] Website: [Link] & videos in [Link]

Dept of ISE, RNSIT 2022-23 Page 29