eg.

This feature allows a user to specify that they own a particular game. The database is updated to store this relationship. Currently, there is no front-end design to support this feature yet, but will certainly be done in the future.

SQL Query:

insert into own
values ('bob6', 112);
select * from own where username = 'bob6';

Output:

Add attributes to Registration process and display them on user info page

Import the dataset into project server. How to generate the “production” dataset and load it into your database. Do not submit the production dataset itself through if it is too big; instead, submit the URL where you download/scrape the raw data (if applicable), and the code that extracts and transforms (or generates) the production dataset. State which features have been implemented and state which files contain the implementation. We expect at least 3 features.

eg.

This feature allows any user to search through all the games in the database by language as well as by substring (so a search of “Fin” will result in “Final Fantasy”) and ordered by rating descending. Currently, there is no front-end design to support this feature yet, but will certainly be done in the future.

SQL Query:

select name, game_image, genre, language, rating
from game
where name like '%car%'
and language = 'English'
order by rating desc;

Output:

A file test-production.sql containing the SQL statements you wrote for Task 8. You may wish to modify some queries to return only the top 10 result rows instead of all result rows (there might be lots for large datasets) and a file test-production.out showing the results of running test-production.sql over the production dataset.

Right now like count is acting very weird

This feature allows a user to get an output of all the games they own, but also include the features additional attributes of the game like genre, language, rating. Currently, there is no front-end design to support this feature yet, but will certainly be done in the future.

SQL Query:

select name, game_image, genre, language, rating
from own, game
where own.gid = game.game_id
and own.username = 'bob6';

Output:

eg.

This feature allows for a user to update his own profile’s attributes, such as language and age. The user table is updated to store these changes. Currently, there is no front-end design to support this feature yet, but will certainly be done in the future.

SQL Query:

update userA
set age = 21
where username = 'bob6';
update userA
set language = 'Mandarin'
where username = 'bob6';
select * from userA where username = 'bob6';

Output: