HTTP 5105 Introduction To MySQL - SQL Commands Fal 2014

MySQL SQL Commands
HTTP 5105 Database Development and Design
HTTP 5105 Database Development and Design 1 November 2014

Introduction
This set of notes will investigate SQL commands with

the emphasis on MySQL

Create Tables
MySQL does allow the creation of a database

In our configuration at Humber you can only work
with predefined databases
These are created by the administrator
You have two
abcd0000_a
abcd0000_b
You will be directed which one to use
Creating Tables
The biggest change when comparing to Oracle is the

data types used
Last we you were provided with a chart outlining the
various datatypes permitted in MySQL, please make
sure you are aware of the differences and the most
commonly used datatypes

Creating Tables Datatypes
Data Type Description
NUMERIC or DECIMAL DECIMAL can also be DEC, fixed point
INTEGER and variations INT most common
FLOAT Represent floating point numbers
CHAR Fixed-length strings, usually followed by a
number CHAR(20), defaults to 1 if no size
VARCHAR Stores variable length strings up to 255,
same length as a CHAR
DATE Stores a date value in format of YYYY-MM-
DD
TIME Stores a time value in the format of
HH:MM:SS

Creating Tables - Engines
MySQL has various storage engines

The MySQL engines are:
MyISAM (default engine)
InnoDB (supports transactions and row-level locking
and foreign keys)
BerkeleyDB
There are other engines than can be used

Creating Tables
Department_id datatype int, also not null so you have to enter a value, auto_increment
so it will assign a value for you, and finally a primary key for the table
Name datatype varchar with a length of 30
The engine this table is created with is the InnoDB engine

Creating Tables
MySQL responds with the

message SQL query has
been executed
successfully
A table is now created, if
you expand your
database in the left pane
you will see the new table
listed
Creating Tables

Creating Tables
After the second table is

created the same
confirmation message is
shown
If you expand the tree
under the database name
you will now see two
tables defined

Creating Tables
After selecting the database from the tree in the left panel you will notice you
see a more detailed description of your tables in the right panel
Creating Tables
What is different?
Datatypes are different
Auto_increment for sequence number generation
The defining of an engine or type
What is the same?
The actual command CREATE TABLE
The open and close parentheses
The column list inside the parentheses
NOT NULL and PRIMARY KEY
FOREIGN KEY definition

Inserting, Updating and Deleting Data
The biggest difference with the INSERT in MySQL is the ability to

insert multiple rows at one time with a single INSERT INTO command

You will notice you

receive confirmation of
how many rows were
inserted to the table
You may wonder about
the two values that were
left as NULL for the
primary key, what
happened?
Let us see what happened to the rows of data we entered

Enter the above command in the SQL window

You will notice the entries for

Human Resources and Marketing
both have a primary key value
This is courtesy of the
auto_increment that was applied
to the table when it was created
Notice it also starts at the next
value above the highest value
inserted already, we supplied 128
so it started at 129

The SQL DELETE statement allows us to delete rows

from a table
The WHERE clause is optional
For the most part it behaves the same as Oracle
MySQL does have a couple of other variations that we
will not go into

There is no WHERE clause specified, what will happen?

Does this give you any indication?
If I click OK I loose all the rows in the table
If I click Cancel nothing will happen, all the rows will remain

As with Oracle the WHERE clause can be used to indicate which rows
are to be deleted
Same as before I am prompted before the deletion takes place
If I click OK I loose all the row specified in the command
If I click Cancel nothing will happen, and the row will remain

The WHERE clause is optional, so if I do not use the WHERE clause all
of the rows would have the update applied to them
In this case I have an

indication 1 row was
updated
The change is applied to
the table right away
Notice there is no
COMMIT or ROLLBACK
commands

You will notice the

employee_id 6651 now
has a job of DBA

SELECT Statement
Should look familiar, there is no difference from what we used

previously in Oracle
SELECT Statement
All of the rows in the

DEPARTMENT table are
displayed
There is a limit of 30 rows
of output imposed on the
query.

SELECT Statement
Can also specify the column names I wish to see in the output

SELECT Statement
Can also use the column

names instead of the *
character
I could also qualify the
table with the column
name, department.name

SELECT Statement
Here only the name

column is now displayed

SELECT Statement

SELECT Statement
You will now notice the

column heading for the
data now reads:
employeeName

SELECT Statement

SELECT Statement
You will notice the AS

keyword is optional, as
with Oracle
Any differences so far
with the SELECT?

SELECT Statement
The WHERE clause can be used to restrict the rows to a specific

criteria
SELECT Statement
The WHERE clause has

limited the output to that
specific criteria
The JOB is Programmer

SELECT Statement
The same basic operators we used in Oracle apply here

in MySQL
=, <, >, >=, <=, !=, <>
IS NULL and IS NOT NULL
AND
OR
NOT
LIKE
BETWEEN AND
SELECT Statement
The DISTINCT keyword will suppress any duplicates in the result set

SELECT Statement
The DISTINCT keyword

suppresses any duplicate
values in the result set

SELECT Statement
The ORDER BY clause will sort the results on the columns and the
sequence specified, in this case it is ascending sequence on the JOB
and then pm descending sequence on the name

SELECT Statement
The ORDER BY behaves

the same as with Oracle
ASC for ascending
sequence
DESC for descending for
descending sequence

SELECT Statement
As with Oracle multiple tables can be used in a SELECT

statement
We can run NATURAL, INNER, and CROSS joins
LEFT and RIGHT joins can also be performed

SELECT Statement

SELECT Statement
The two columns being

displayed had to be
qualified since the column
NAME appears in both
tables

SELECT Statement
This format corresponds to the Oracle ANSI syntax

SELECT Statement
The JOIN keyword can

also be used as shown it
this output

SELECT Statement
In this screen capture you will notice there is no join condition being
specified
SELECT Statement
There are 16 rows of

output, every row of the
EMPLOYEE table is joined
with every row on the
DEPARTMENT table
4 rows * 4 rows is 16 rows

SELECT Statement
In this screen capture you will notice there is the cross join condition
being specified
SELECT Statement
The CROSS JOIN

keywords also work with
MySQL
Indicates there is no join
condition being used
between the two tables

SELECT Statement
The GROUP BY function can also be used to group data in the result
set together
SELECT Statement
The COUNT function has

counted the occurrences
of the job and displayed
the result in the output

SELECT Statement
Here the entire table is treated as one group

SELECT Statement
The result says there are

three distinct job values in
the table

SELECT Statement
Not the use of the HAVING clause to restrict the groups being
displayed
SELECT Statement
The HAVING clause is

being used here display
the rows returned by the
group by that are equal to
only a value of 1

Transactions
We made a note before that the COMMIT and

ROLLBACK statements were not being used
In the format we used previously value for Autocommit
is set to being active
Set autocommit=0;
This is the default behaviour
Set autocommit=1 will set it for your session, if you log
off it is gone and has to be reset next time you connect

Transactions
The above table has been created to look at transactions

Transactions
We will use this table to

look at transactions in
MySQL
We do have to insert
some data rows to the
table

Transactions
The above rows are being inserted into the ACCOUNTS table
Transactions
Confirmation the three

rows were inserted into
the table

Transactions
The transaction begins with the keywords START TRANSACTION
The COMMIT keyword will make the change permanent in the table ,
a ROLLBACK could also be used
GROUP BY Revisited
Since there was a table now with a numeric value, I decided to add
to the various group functions So here are the ADD, SUM, MIN, and
MAX function in use

Transactions
The various group

function results are
shown

Conclusions
I think you can agree there are far more similarities

between the SQL flavours then there are differences
This is the beauty of having a SQL standard
Most database vendors do adhere quite close to the
standard
There are a few places where the syntax is not
identical

HTTP 5105 Introduction To MySQL - SQL Commands Fal 2014

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

HTTP 5105 Introduction To MySQL - SQL Commands Fal 2014

Diunggah oleh

Hak Cipta:

Format Tersedia

MySQL SQL Commands

HTTP 5105 Database Development and Design

HTTP 5105 Database Development and Design 1 November 2014

This set of notes will investigate SQL commands with

HTTP 5105 Database Development and Design 2 November 2014

MySQL does allow the creation of a database

The biggest change when comparing to Oracle is the

HTTP 5105 Database Development and Design 4 November 2014

HTTP 5105 Database Development and Design 5 November 2014

MySQL has various storage engines

HTTP 5105 Database Development and Design 6 November 2014

Name datatype varchar with a length of 30

The engine this table is created with is the InnoDB engine

MySQL responds with the

HTTP 5105 Database Development and Design 9 November 2014

After the second table is

HTTP 5105 Database Development and Design 10 November 2014

HTTP 5105 Database Development and Design 12 November 2014

The biggest difference with the INSERT in MySQL is the ability to

HTTP 5105 Database Development and Design 13 November 2014

You will notice you

Let us see what happened to the rows of data we entered

HTTP 5105 Database Development and Design 15 November 2014

You will notice the entries for

HTTP 5105 Database Development and Design 16 November 2014

The SQL DELETE statement allows us to delete rows

HTTP 5105 Database Development and Design 17 November 2014

There is no WHERE clause specified, what will happen?

HTTP 5105 Database Development and Design 18 November 2014

Does this give you any indication?

If I click OK I loose all the rows in the table

HTTP 5105 Database Development and Design 19 November 2014

Same as before I am prompted before the deletion takes place

If I click OK I loose all the row specified in the command

HTTP 5105 Database Development and Design 21 November 2014

In this case I have an

HTTP 5105 Database Development and Design 23 November 2014

You will notice the

HTTP 5105 Database Development and Design 24 November 2014

Should look familiar, there is no difference from what we used

All of the rows in the

HTTP 5105 Database Development and Design 26 November 2014

HTTP 5105 Database Development and Design 27 November 2014

Can also use the column

HTTP 5105 Database Development and Design 28 November 2014

Here only the name

HTTP 5105 Database Development and Design 29 November 2014

HTTP 5105 Database Development and Design 30 November 2014

You will now notice the

HTTP 5105 Database Development and Design 31 November 2014

HTTP 5105 Database Development and Design 32 November 2014

You will notice the AS

HTTP 5105 Database Development and Design 33 November 2014

The WHERE clause can be used to restrict the rows to a specific

The WHERE clause has

HTTP 5105 Database Development and Design 35 November 2014

The same basic operators we used in Oracle apply here

HTTP 5105 Database Development and Design 37 November 2014

The DISTINCT keyword

HTTP 5105 Database Development and Design 38 November 2014

HTTP 5105 Database Development and Design 39 November 2014

The ORDER BY behaves

HTTP 5105 Database Development and Design 40 November 2014