Skip to main content

PHP Session Handling with MySQL

There are many ways that session handling can be used to provide a dynamic and non-static experience for
the end user. Sessions can be used for providing a more personal experience for the end users by keeping
track of them as they roam through a site providing content that is more tailored to their likes and dislikes
(by monitoring the choices they make in what they choose to view). Sessions can also be used to make sure
that only those who have a valid username and password can gain access to a specific part of a site, or in
the case of any online store; keep track of what is in the shopping chart at any given time. These are just
some examples of how session handling have added value to the web experience.
MySQL is a perfect companion to session handling by being able to help with the process of storing and
retrieving the data that gives extra life to the session handling capabilities. With the ability to connect
multiple types of information (data stored in the database selected and used in such a way to add value) to
the user at the database level can provide a much more dynamic and personal experience for the end user.


MySQL Handling Logins Example

It is quite common to use a database to handle the login storage and retrieval of the associated data needed
for ensuring a secure login and personal experience. However, it is also handy to provide a means to allow
returning users to skip the login when they move from page to page in a site or return to the site within a
specified time period.

Storing MySQL Session Data

Before using MySQL to store session data, there must be a place to put the data. This involves creating a
table that contains the information necessary to manage the login of a user into a site. The following table
will be used to manage the storage of the login information that will be used by PHP to manage logins:

CREATE TABLE `customers` (
`customerEmail` VARCHAR(40) NOT NULL,
`lname` VARCHAR(25) NOT NULL,
`fname` VARCHAR(25) NOT NULL,
`title` ENUM('Mr.', 'Mrs.', 'Miss', 'Ms.', 'Dr.');
`passwd` VARCHAR(30),
PRIMARY KEY (`customerEmail`)
);

The idea of using the customerEmail as the login in identifier has become standard practice in many web
applications these days. As far as an email being a primary identifier for the customer, it is perfect; It is
unique (no two people could have the exact same e-mail account), it is specific to the user and it is an
alternate means to contact the user. In this table, there could be additional columns used to support other
areas of the application; however, for the purpose of this training, this table will suffice.

Comments

Popular posts from this blog

PHP INTRODUCTION

                     PHP  (recursive acronym for  PHP: Hypertext Preprocessor ) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. PHP stands for  P HP:  H ypertext  P reprocessor PHP is a server-side scripting language, like ASP PHP scripts are executed on the server PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Generic ODBC, etc.) PHP is an open source software PHP is free to download and use Why PHP? PHP runs on different platforms (Windows, Linux, Unix, etc.) PHP is compatible with almost all servers used today (Apache, IIS, etc.) PHP is FREE to download from the official PHP resource:  www.php.net PHP is easy to learn and runs efficiently on the server side What can PHP do? Anything. PHP is mainly focused on server-side scripting, so you can...

Self Joins

A table name is always ambiguous when table is joined to itself using a self-join. For example, the Country table in the world database contains an IndepYear column indicating the year in which each country achieved independence. To find all countries that have the same year of independence as some given country, a self-join can be used. However, the query cannot be written like this: mysql> SELECT IndepYear, Name, Name -> FROM Country JOIN Country -> ON IndepYear = IndepYear AND Name = 'Qatar'; ERROR 1066 (42000): Not unique table/alias: 'Country' Furthermore, the ambiguity cannot be removed from column references by preceding them with table name qualifiers because the names remain identical: mysql> SELECT Country.IndepYear, Country.Name, Country.Name -> FROM Country JOIN Country -> ON Country.IndepYear = Country.IndepYear -> AND Country.Name = 'Qatar'; ERROR 1066 (42000): Not unique table/alias: 'Country' It ...