4.1 What is the term given to the GameID field in the tblGamesPlayed table? 4.1.2 How many games will each player be able to play per day based on the construction of the database? Choose the answer from the options (A–C) provided below - NSC Information Technology - Question 4 - 2017 - Paper 2

The answer is C: Any number of games per day. The design of the database allows players to participate in multiple games without restrictions on the number of games played in a day.

The message is displayed because PlayerID F566 exists in the tblGamesPlayed table, indicating that there are associated records. In a relational database, you cannot delete a primary key that is still being referenced by a foreign key in another table, to maintain data integrity.

To delete the player with PlayerID F566, you first need to delete all related entries in the tblGamesPlayed table that reference this PlayerID. Once those records are removed, you can then delete the player from the tblPlayers table.

The SQL statement for this query would be:

SELECT * FROM tblGamesPlayed WHERE TimePlayed >= '12:00:00' AND TimePlayed <= '15:00:00';

To update the scores, the SQL statement would be:

UPDATE tblGamesPlayed SET Score = Score * 1.15 WHERE GameID = 'G103';

This SQL statement will return the GameID and the highest score achieved for each game sorted from highest to lowest. The output will display GameIDs along with their maximum scores from the tblGamesPlayed table.

This SQL statement will return the GameNumber along with a concatenated reference name made up of the first letters of the player's PName and PSurname. The output will look something like:

GameNumber: 1, Reference: Y & X

Adding an ID number and date of birth field could lead to data redundancy if these fields are already represented elsewhere in the system, like in a user account database or student database that maintains unique ID numbers and birth dates.

1. Parameterized Queries: Use prepared statements with parameterized queries to avoid passing raw user input directly into SQL commands, thus preventing malicious injections.
2. Input Validation: Implement robust input validation to sanitize user inputs, ensuring that only valid data types are accepted and that dangerous characters are filtered out.