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 correct answer is C: Any number of games per day. This is allowed because there is no restriction in the database schema that limits the number of games a player can participate in within a single day.

The message indicates that PlayerID F566 cannot be deleted from the tblPlayers table because it has related entries in the tblGamesPlayed table. This implies a Foreign Key constraint that prevents deletion to maintain referential integrity.

A possible solution is to first delete any entries corresponding to PlayerID F566 from the tblGamesPlayed table. Once those entries have been removed, PlayerID F566 can then be deleted from the tblPlayers table.

To display all details of the games played in the specified time range, the SQL statement would be:

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

The SQL statement to update the scores would be:

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

The output of the SQL statement will return the maximum score achieved for each game in the tblGamesPlayed table, and the results will be sorted in descending order based on the maximum score.

The output of the SQL statement will produce a list of game numbers along with the initial letters of the player's first and surname, concatenated with a space in between. The output will specifically correspond to the first record in the tblGamesPlayed table.

Adding an ID number and a date of birth field to the tblPlayers table will likely result in data redundancy if such information is already being stored in another table or if it can be derived from existing data. This duplication of data can lead to inconsistencies and increased storage costs.

1. Use Prepared Statements: This involves using SQL statements that are precompiled and parameters are passed through, which can help prevent malicious SQL code from manipulating the database.
2. Validate Input: Ensuring that all user-supplied input is validated and sanitized before being processed can minimize the risk of SQL injections.