Now we did set up the MySQL server
in the last lecture,
and now we are ready to dive into it.
But before we write our queries
and before we create databases,
we have to understand the structure
of the things we just installed
and we'll be working with.
Because what we actually did
is we installed MySQL.
Now that's actually the software itself.
It includes the database server,
which is the thing that will
actually host our databases,
and which is the thing with
which we connect to stored data or fetch data.
And then also for example,
there's MySQL Workbench Tool.
There's UI client,
that's all a part of the MySQL software package.
And it's indeed that server
which we started in the last lecture as well,
which is now running on our local machine
and to which we can connect
to store data there or fetch data.
So this is the actual server that will host our databases
and that's not important.
In the last lectures and in the last section
I often said,
Sequel Database,
when I meant a solution like MySQL.
But actually the concrete databases
are not what we installed.
Instead we installed that server and MySQL Workbench,
but the databases are groupings,
containers that are actually hosted by that server.
So on that server,
we will now be able to create multiple databases,
relational databases by default,
since we're using MySQL
and MySQL is about relational databases.
But it's these concrete databases
with which we'll interact
when we later run our queries and so on.
So we installed MySQL.
That was actually the installation
of a server and MySQL Workbench.
Then we started the server
and then we'll start
and create databases on that server.
And these databases are also sometimes called Schemas.
Here in the MySQL Workbench,
we have this Administration and Schemas tab
and Schemas actually holds all the databases
we have on this database server,
to which we connected here.
And we have one database by default here,
which holds System Information.
As you can see,
it has one table in it.
But we can also add our own databases,
which then can hold our application data.
And then as you just saw in that MySQL Workbench Tool,
every database can have multiple tables
and it's the tables that will
hold the actual data records later.
So it's the tables that have these columns and rows,
and it's the tables that hold the actual data.
But we can have multiple databases with multiple tables
simply depending on what we need
for the website we're building.
For simple websites like the ones we're building here,
you will very often only have one database
on that database server.
But for more complex websites
you could have multiple databases in a single server.
And now that we know that.
Let's start working with MySQL
and let's start creating some databases
and tables
and data.