SQL for Beginners
basix

SQL for Beginners

Most modern web applications today interact with databases, usually with a language called SQL. Lucky for us, this language is quite easy to learn. In this article, we are going to start with some basic SQL queries and use them to interact with a MySQL database.

What You Need

SQL (Structured Query Language) is a language designed for interacting with relational database management systems (RDBMS), like MySQL, Oracle, Sqlite etc… To perform the SQL queries in this article, I suggest that you have MySQL installed. I also recommend phpMyAdmin as a visual interface to MySQL.

The following applications make it very easy to install both MySQL and phpMyAdmin on your local machine:

We are going to use command line for queries. WAMP already comes with a MySQL Console. For MAMP, you may want to read this article.

CREATE DATABASE: Creating a Database

Here comes our very first query. We are going to be creating a database to work with.

First, open up your MySQL Console and login. For WAMP, the default password is blank. For MAMP, the password should be ‘root’ by default.

After logging in, type this query and hit enter:

CREATE DATABASE my_first_db;

Note that semicolon (;) is added at the end of the query, just like at the end of lines of code.

Also, the special words ‘CREATE DATABASE’ are case insensitive, along with all special words in SQL. But for the sake of readability, we will be writing them in uppercase.

Optional: Character Set and Collation

If you would like to set the default character set and collation, you can write the same query like this instead:

CREATE DATABASE my_first_db DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

Here is a list of supported character sets and collations in MySQL.

SHOW DATABASES: List All Databases

This query is used to get a list of all databases you have.

DROP DATABASE: Delete a Database

You can delete an existing database with this query.

Be careful with this query, because it gives you no warnings. If you have tables and data under the database, they will all be deleted instantly.

USE: Selecting a Database

This technically is not a query. It is a ‘statement’ and does not require a semicolon at the end.

It tells MySQL to select a default database to work with, for the current session. Now we are ready to create tables and do other things under this database.

What is a Database Table?

You can think of a database table like a spreadsheet or csv file that holds structured data.

Just like in this example, tables have column names, and rows of data. With SQL queries we can create these tables. We can also add, read, update and delete the data.

CREATE TABLE: Creating a Table

With this query we can create tables in the database. Unfortunately the MySQL documentation is not very friendly for new learners. The structure of this type of query can get very complex, but we will start with an easy one.

The following query will create a table with 2 columns.

CREATE TABLE users (
	username VARCHAR(20),
	create_date DATE
);

Note that we are able to write a query in multiple lines, and even use tabs for indentation.

First line is easy. We just create a table named ‘users’. Following that, in parantheses, we have a list table columns separated by commas. After each column name, we have a data type, such as VARCHAR or DATE.

VARCHAR(20) means that the column is a string type, and can be a maximum of 20 characters long. DATE is also a data type that is specifically used for storing dates, in this format: ‘YYYY-MM-DD’.

PRIMARY KEY

Before we run that query, we should also include a column for ‘user_id’, which will be a PRIMARY KEY. Without getting too much into the details, you can think of a PRIMARY KEY as a way to identify each row of data in a table.

Now the query becomes:

CREATE TABLE users (
	user_id INT AUTO_INCREMENT PRIMARY KEY,
	username VARCHAR(20),
	create_date DATE
);

INT makes this a 32bit integer type (i.e. numeric). AUTO_INCREMENT automatically generates a new id number every time we add new rows of data. It is not required, but makes it much more convenient.

This column does not have to be an integer, but it is the most commonly used type. Having a PRIMARY KEY column also is not required, but it is strongly recommended for good database design and performance.

Let’s run the query:

SHOW TABLES: List All Tables

This query allows you to get a list of tables that are currently in the database.

EXPLAIN: Show Table Structure

To see the structure of an existing table, you can use this query.

Fields (aka. columns) are listed in the results, with their properties.

DROP TABLE: Delete a Table

Just like DROP DATABASES, this query deletes a table and its contents, without a warning.

ALTER TABLE: Modify a Table

This query also can have quite a complex structure because of the multitude of changes it can perform on a table. Let’s look at some simple examples.

(Make sure to re-create the table we just dropped or the following queries obviously won’t work.)

Add a Column

ALTER TABLE users
	ADD email VARCHAR(100)
	AFTER username;

Thanks to the readability of SQL, I don’t think that query even needs an explanation.

Remove a Column

That was also very simple. But use it with caution as it permanently removes data without a warning.

Re-add the email column because we are going to be using it later:

ALTER TABLE users
	ADD email VARCHAR(100)
	AFTER username;

Modify a Column

Sometimes you may want to change the properties of a column, so you don’t have to delete and recreate it.

That renamed the username column to ‘user_name’ and changed the type from VARCHAR(20) to VARCHAR(30). A change like this should not disturb any of the existing data in the table.

INSERT: Add Data to a Table

Let’s add some data into the table using this query.

As you can see, VALUES() contains the list of field values, separated by commas. The string values are enclosed in single quotes. And the values need to be in the order of the columns that were defined when we created the table.

Note that the first value is NULL for the PRIMARY KEY field we called ‘user_id’. We do this so that an id is automatically generated, because the column is set to AUTO_INCREMENT. When entering a row of data for the first time, the id will be 1. Next inserted row will be 2 and so on…

Alternate Syntax

Here is another syntax for inserting rows.

This time we are using the keyword SET instead of VALUES, and it is not followed by paratheses. There are a few things to note here:

  • A column can be omitted. For example we did not assign a value to user_id, which will default to the AUTO_INCREMENT functionality. If you omit a VARCHAR column, it would default to an empty string (unless a different default value was specified during table creation).
  • Each column has to be referenced by its name. Because of this, they can be in any order, unlike the previous syntax.

Alternate Syntax 2

Here is yet another syntax.

Again, since each column is referenced by name, they can be in any order.

LAST_INSERT_ID()

You can use this query to get the AUTO_INCREMENT id for the last inserted row, in the current session.

NOW()

I think it is a good time to demonstrate how you can use a MySQL function inside your queries.

The NOW() function returns the current date. So you can use it to automatically set a DATE column to the current day while inserting a new row.

Note that we received a warning from MySQL, but it is not a big deal. The reason is that NOW() actually returns time information as well.

But the create_date column we created only contains the date, and not the time, therefor the returned data was truncated. We could use the CURDATE() function instead, which returns just the date, but the data stored at the end would be the same either way.

SELECT: Read Data from a Table

Obviously the data we added would be useless unless we can read it. This is where the SELECT query comes in.

Here is the simplest possible SELECT query for reading from a table:

In this case, the asterisk (*) means that we asked to fetch all the columns from the table. If you want only specific columns, the query would look like this:

WHERE Clause

More often than not, we are only interested in some of the rows, and not all. For example, let’s say we want the email address for the user ‘nettuts’.

Think of it like an IF statement. WHERE allows you to put conditions in the query for the results you are looking for.

Note that for the equality condition, only a single equal sign is used (=), instead of double (==) which you might be used to from programming.

You can use other comparison conditions too:

AND and OR can be used to combine conditions:

Note that numeric values do not have to be inside quotes.

IN()

This is useful for matching multiple values.

LIKE

This allows you to do wildcard searches.

Percentage sign (%) is used as the wildcard.

ORDER BY Clause

If you want the results to be returned in a specific order, use this clause:

The default order is ASC (i.e. ascending). You can add DESC to reverse order it.

LIMIT … OFFSET …

You can limit the number of returned results.

LIMIT 2 just gets the first 2 results. LIMIT 1 OFFSET 2 gets 1 result, after the first 2 results. LIMIT 2, 1 means the same thing, but note that the first number is the offset and the second number is the limit.

UPDATE: Update Data in a Table

This query is used for updating the data in a table.

Most of the time, it is used with a WHERE clause, because you would want only specific rows to be updated. If a WHERE clause is not provided, all rows would be updated with the same changes.

You can also use a LIMIT clause to limit the number of rows to be updated.

DELETE: Delete Data from a Table

Just like UPDATE, this query is also usually used with a WHERE clause.

TRUNCATE TABLE

To delete the entire contents of a table, you can just do this:

DELETE FROM users;

But it is usually more performance efficient to use TRUNCATE instead.

TRUNCATE also resets the AUTO_INCREMENT numbers so a new row will again have the id 1. But this does not happen with a DELETE query, and the counter keeps going up.

Escaping String Values and Special Words

String Values

Certain characters need to be escaped, otherwise you can have problems.

Backslash (\) is used for escaping.

This is also very important for security reasons. Any user input going into the database needs to be properly escaped. In PHP, you use the mysql_real_escape_string() function or use prepared statements since they do escaping automatically.

Special Words

Since MySQL has many special words like SELECT or UPDATE, you can prevent collision by putting quotes around your table and column names. But these are not the regular quotes; you need to use the backtick (`) character.

Let’s say you want to add a column named ‘delete’ for some reason:

Conclusion

Thank you for reading the article. Hopefully I was able to show you that SQL has an easy learning curve yet it is very powerful.

Please leave your comments and questions, and have a great day!

Ready to take your skills to the next level, and start profiting from your scripts and components? Check out our sister marketplace, CodeCanyon.

CodeCanyon

Note: Want to add some source code? Type <pre><code> before it and </code></pre> after it. Find out more
  • ShadowAssassin

    Thank you for this tutorial ^__^

    • http://www.phpandstuff.com Burak
      Author

      You’re welcome :)

  • Abhin Sharma

    nice tutorial…. :)

  • http://www.gabrielbianconi.com/ GabrielBianconi

    Nice tut… :D

  • Matthew

    Do you know a way to add a column description after it’s already been created? I know how to do it when you first create the column, but not after the fact.

    • http://www.phpandstuff.com Burak
      Author

      ALTER TABLE `table_name` CHANGE `column_name` `column_name` INT NOT NULL COMMENT ‘blah blah’

      Make sure to match the original properties of the column, so they don’t get changed. (like NOT NULL or UNSIGNED etc…)

  • http://www.eirestudio.net Keith

    Nice one Burak.

    Got an idea for a tut: Could you write up a tutorial about database relationships in a fun way. For example, create a basic DVD library app that has a few tables, dvd table, actors table etc etc?

    • http://www.phpandstuff.com Burak
      Author

      Yea, I would like to write about database relationships. We’ll see.

      • http://myfacefriends.com Myfacefriends

        Thanks mate! nice tuts!

  • http://webx.pl MaczX

    Why in CMD? This isn’t good way to learn, I think.

    • Eric

      Think of it as under the hood. Similar to the way Mr. Way shows JS under the hood. When you are doing basic CRUD it is ok to learn from looking at someone sticking a tiny sql statement in a php variable. But, when you are writing super complex business logic in an SQL statement whether it is MySql, SQL*Plus, or T-SQL use a sql editor to become familiar with the data you are coding.

      There is more to IT than just a IDE….

    • Cris

      Why is a bad way to learn? Most people take GUIs for granted and don’t necessarily know what is actually happening.

      I think its the best way to learn, from the basics, then use tools to help you get the job done quicker.

    • http://zck.in Zachary

      It’s exactly the same as writing SQL statements in PHP… Why wouldn’t you do it at the command line?

  • http://www.jennamolby.com Jenna Molby

    Great tutorial! :)

  • juan

    thx

  • http://whatupderek.com Derek Reynolds

    Definitely going to be my goto resource when I can’t remember some part of the syntax. Thanks!

  • http://miralize.com Sean O’Grady

    This would have been sooo helpful the other day when I had my exam. Ohh well. Cheers!

  • http://www.urbanvideos.tv alan

    Yes sometimes you can’t remember some part of the syntax.So this is very helpful .thanx man !

  • Kyle

    stored procedures?

  • http://www.graphicom.ca ExtremeLongName To see how it looks hehe

    Very interesting article

  • http://spotdex.com/ David Moreen

    Good stuff, I still find myself using copy and paste when working with SQL. I really should get it down.

  • http://www.geniuzdesigns.de g3niuz

    seems useul..

    thanks ;d

  • Darrel

    I have used several (shared) web hosts and none of them allow access to the MySQL console. All used phpMyAdmin. To me, a tut on MySQL would be more useful when demonstrated using phpMyAdmin than the MySQl console.

    • http://www.phpandstuff.com Burak
      Author

      You can just click the SQL tab inside phpMyAdmin to run any of these queries.

  • Imran Khan

    It’s a nice piece of work Burak.. keep it up…. , and thanks for sharing.

  • http://tomleo.com Tom

    Great tutorial, I work so much in CMS’s where theres always a layer of abstraction of things like this, or I’ll just use phpmyadmin, so it’s great to learn a thing or to in the command line.

    BTW if your on ubuntu or the equivalent then you can do the following

    sudo mysql -p

  • http://www.galaxydesign.com.au Sam

    great stuff… keep it coming….

  • http://butenas.com Ignas

    not bad for beginners :) All in one place. And of course for person who works with mysql for a years there are no interesting points here. But congrats that you really helped for the beginners, I thinks they now are really happy :)

  • http://bwebi.com barat

    Well … nothing new for now, but … maybe in next one – indexes, relations, fulltext search, regexp in SQL, Big Table vs JOINs, JOINs itself, performance tricks (but there was one tutorial about this on evanto I think)

    • arnold

      yeah I agree with you
      join and some more joins are sometimes cool to learn in sql

  • http://laranzjoe.blogspot.com lawrence77

    Very good for Beginners….

  • http://www.aaronbentley.co.uk Aaron Bentley

    man i wish these tuts were about when i started webDev a few years ago.
    Nice article btw.

  • http://sonergonul.com Soner Gönül

    Great..

    Nice Tutorial

    Thanks..!

  • http://www.weimit.com Oli

    Excellent tutorial .. BUT, the very last bit is NOT a good tip.
    You should not, for ANY reason , name a column with a MySQL reserved word.

  • andrei.tarykin

    Good tutorial. Thanks!

  • http://9lessons.blogspot.com Srinivas Tamada

    Very best..

  • http://blogorbrowse.com John Samuel

    Quite a useful tutorial. Looking forward to see a mysql tutorial

  • http://evansofts.com Evan-XG

    very nice tutorials, I am gonna follow you righ now.

  • http://parenting.pl Marcin

    Is there no Plus tutorial this Wednesday?

  • http://www.creative24studios.com Neil Berry

    Great tutorial! Thanks

  • http://davekingsnorth.com Dave

    With so many other things out there to learn, I’d rather stick to phpmyadmin. Good article for those who use SQL though

  • Commenter

    LOOOOOOOL Dave, Learn other stuff? Mate, when you code something and you want to use the DB with then you DONT use PHPMyAdmin – you WRITE Sql.

    Excellent tutorial D:

    • Dave

      Your right I should have read on. At a glance I saw that it involved creating tables and displaying a list of databases and decided not to continue. Sure I use SELECT and INSERT in a php script but why wouldn’t you create your tables and set things such as auto increment before hand in phpmyadmin.

      I’m sure there is a reason and I’d like to learn when it’s useful.

      Did you actually laugh out loud with multiple o’s in the middle? or are you just a prick who often writes in caps and mocks the beginners when they accidently make a stupid comment

  • http://www.brettjankord.com Brett Jankord

    Great tutorial, love to see more like this.

  • Maciej

    Great tutorial for beginners! Thank you :)

  • Marcio Toledo

    I’ve been working with SQL for 3 years, the article is too basic for me, but its pretty well done!

    One doubt I never got an answer: Why do most of the database management programs icons or database icons have dolphins??

    • http://www.phpandstuff.com Burak
      Author

      MySQL logo has dolphin. PostgreSQL has elephant.

  • Pachito Marco Calabrese

    Nice!! i’d like see more SQL tuts!!

  • TuNG

    The basic stuff should be always reviewed again and again.

    Thank you so much for this useful article

  • http://www.fact-o-tron.com Stimul8d

    Nice work man. Some of it isn’t strictly ANSI SQL so can’t be used with other RDBMS’ but a good overview all the same.

  • http://www.aplacetocode.com Aaron

    Great post, very easy to follow and very informative.

  • WebVisitor

    Good job, excellent tutorial, thanks for share it.

  • Mourad

    Thanks Burak. All your tutorials are absolutely GREAT !

  • http://www.jeffadams.co.uk Jeff Adams

    For any aspiring web developer they NEED to understand databases – even if its just how to update, add, delete etc. This tutorial started with the basics and got progressively more advanced so well done.

    My ONLY critisim is that it’s not easily digestable because of the screenshots e.g. not much cut and paste available.

    Thats being very picky though, a very good tutorial well done.

  • http://giovanigenerali.com Giovani Generali

    Nice tut.. :)

  • http://tutorialblog.info tutorial blog

    thank. it useful

  • http://www.danblee.com Dan B. Lee

    I’ve never seen a tutorial based on the console. Most of the time they go with the browser interface and go into the code just a bit, but never browser. This is brilliant. Good work.

  • http://www.slideaway.ca/ jamEs

    This may just be my perception, but anything involving the command line is not for beginners. I’ve learned a fair bit poking around using PHPmyadmin on my own, but I find almost by definition using the command line is really getting your hand dirty.

  • http://inprogress identitysquar

    Thanks for the great tut. getting plus membership tonight

  • http://www.peakxel.com Afrio

    This is the greatest tutorial I’ve been waiting all my life. Thanks

  • Rockstar79

    Great tutorial…very clear and easy to understand

    Thanks!