Course Content
Practice SQL with Cinema Database
Practice SQL with Cinema Database
Cinema's database
Welcome to the SQL Bootcamp! In this course, we'll be working with data on cinemas and movies. We have data stored in the database with the next schema:
This database consists of six tables:
director
contains info about te various movies directors.manager
contains a list of cinemas' managers.genre
stores list of movies genres.cinema
contains a list of cinemas. Each cinema haslabel
column as a cinema's name,address
,manager_id
that refers tomanager
table, andcity
in which the cinema is located.movie
table stores data aboutlabel
,year
of release,genre_id
, anddirector_id
, as well as the movierating
.schedule
table contains records of ids' pairs:cinema_id
andmovie_id
. It corresponds to which movie has the box office in which cinema and the total sales of this movie in this cinema.
Here we can see the records of the movie
table.
To see other tables' content, run the select
query using the code editor.
Note that some fields may contain NULL values; some movies may not be at the box office, or some directors have not produced films among present in the movie
table. This database is created for studying, but it represents the real-like databases that can contain imperfect data or some extra data. Don't be afraid of it, but keep in mind.
The order of the rows matters. If you are unable to submit a valid query due to Incorrect Output, double check that the rows are arranged as requested in the assignment. Then check that the column names are correct.
Thanks for your feedback!
Cinema's database
Welcome to the SQL Bootcamp! In this course, we'll be working with data on cinemas and movies. We have data stored in the database with the next schema:
This database consists of six tables:
director
contains info about te various movies directors.manager
contains a list of cinemas' managers.genre
stores list of movies genres.cinema
contains a list of cinemas. Each cinema haslabel
column as a cinema's name,address
,manager_id
that refers tomanager
table, andcity
in which the cinema is located.movie
table stores data aboutlabel
,year
of release,genre_id
, anddirector_id
, as well as the movierating
.schedule
table contains records of ids' pairs:cinema_id
andmovie_id
. It corresponds to which movie has the box office in which cinema and the total sales of this movie in this cinema.
Here we can see the records of the movie
table.
To see other tables' content, run the select
query using the code editor.
Note that some fields may contain NULL values; some movies may not be at the box office, or some directors have not produced films among present in the movie
table. This database is created for studying, but it represents the real-like databases that can contain imperfect data or some extra data. Don't be afraid of it, but keep in mind.
The order of the rows matters. If you are unable to submit a valid query due to Incorrect Output, double check that the rows are arranged as requested in the assignment. Then check that the column names are correct.
Thanks for your feedback!
Cinema's database
Welcome to the SQL Bootcamp! In this course, we'll be working with data on cinemas and movies. We have data stored in the database with the next schema:
This database consists of six tables:
director
contains info about te various movies directors.manager
contains a list of cinemas' managers.genre
stores list of movies genres.cinema
contains a list of cinemas. Each cinema haslabel
column as a cinema's name,address
,manager_id
that refers tomanager
table, andcity
in which the cinema is located.movie
table stores data aboutlabel
,year
of release,genre_id
, anddirector_id
, as well as the movierating
.schedule
table contains records of ids' pairs:cinema_id
andmovie_id
. It corresponds to which movie has the box office in which cinema and the total sales of this movie in this cinema.
Here we can see the records of the movie
table.
To see other tables' content, run the select
query using the code editor.
Note that some fields may contain NULL values; some movies may not be at the box office, or some directors have not produced films among present in the movie
table. This database is created for studying, but it represents the real-like databases that can contain imperfect data or some extra data. Don't be afraid of it, but keep in mind.
The order of the rows matters. If you are unable to submit a valid query due to Incorrect Output, double check that the rows are arranged as requested in the assignment. Then check that the column names are correct.
Thanks for your feedback!
Welcome to the SQL Bootcamp! In this course, we'll be working with data on cinemas and movies. We have data stored in the database with the next schema:
This database consists of six tables:
director
contains info about te various movies directors.manager
contains a list of cinemas' managers.genre
stores list of movies genres.cinema
contains a list of cinemas. Each cinema haslabel
column as a cinema's name,address
,manager_id
that refers tomanager
table, andcity
in which the cinema is located.movie
table stores data aboutlabel
,year
of release,genre_id
, anddirector_id
, as well as the movierating
.schedule
table contains records of ids' pairs:cinema_id
andmovie_id
. It corresponds to which movie has the box office in which cinema and the total sales of this movie in this cinema.
Here we can see the records of the movie
table.
To see other tables' content, run the select
query using the code editor.
Note that some fields may contain NULL values; some movies may not be at the box office, or some directors have not produced films among present in the movie
table. This database is created for studying, but it represents the real-like databases that can contain imperfect data or some extra data. Don't be afraid of it, but keep in mind.
The order of the rows matters. If you are unable to submit a valid query due to Incorrect Output, double check that the rows are arranged as requested in the assignment. Then check that the column names are correct.