Relations, tuples, and attributes in DBMS Theory - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a relation with attributes.

DBMS Theory

CREATE TABLE Students ([1] VARCHAR(50), Age INT);

Drag options to blanks, or click blank then click option'

AName

BTuple

CAttribute

DRelation

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Tuple' or 'Relation' instead of an attribute name.

The code defines a table with an attribute called Name. Attributes are the columns in a relation.

2fill in blank

medium

Complete the code to insert a tuple into the relation.

DBMS Theory

INSERT INTO Students VALUES ('Alice', [1]);

Drag options to blanks, or click blank then click option'

A'Student'

B20

C'Age'

DRelation

Attempts:

3 left

💡 Hint

Common Mistakes

Using attribute names or relation names instead of actual data values.

The code inserts a tuple with values 'Alice' and 20 into the Students relation. Tuples are rows of data.

3fill in blank

hard

Fix the error in the relation definition by completing the blank.

DBMS Theory

CREATE TABLE Employees (ID INT, [1] VARCHAR(100));

Drag options to blanks, or click blank then click option'

AAttribute

BRelation

CTuple

DName

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Tuple' or 'Relation' as attribute names.

The second attribute should be a valid column name like Name. 'Tuple' and 'Relation' are not valid attribute names.

4fill in blank

hard

Fill both blanks to create a tuple with correct attribute values.

DBMS Theory

INSERT INTO Products VALUES ([1], '[2]');

Drag options to blanks, or click blank then click option'

A101

BLaptop

CProduct

DRelation

Attempts:

3 left

💡 Hint

Common Mistakes

Using attribute or relation names instead of actual data values.

The tuple inserted has an ID of 101 and a product name 'Laptop'. These match the attributes of the Products relation.

5fill in blank

hard

Fill all three blanks to define a relation and insert a tuple correctly.

DBMS Theory

CREATE TABLE [1] (ID INT, [2] VARCHAR(50));
INSERT INTO [3] VALUES (1, 'John');

Drag options to blanks, or click blank then click option'

ACustomers

BName

DRelation

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Relation' as a table or attribute name.

The relation is named Customers with attributes ID and Name. The tuple inserted belongs to the Customers table.

Practice

1. What does a tuple represent in a database relation?

easy

A. A key used to identify records

B. A column or attribute of the table

C. A single row or record in the table

D. The entire table itself

Solution

1. Step 1: Understand the definition of a tuple

   A tuple is defined as a single row in a relation, representing one record.

2. Step 2: Differentiate tuple from attributes and relation

   Attributes are columns, and the relation is the whole table, so tuple must be a row.

3. Final Answer:

   A single row or record in the table -> Option C

4. Quick Check:

   Tuple = row [OK]

Hint: Tuple means one row or record in a table [OK]

Common Mistakes:

• Confusing tuple with attribute (column)
• Thinking tuple is the whole table
• Mixing tuple with keys

2. Which of the following correctly describes an attribute in a relation?

easy

A. A single row in the table

B. A column representing a data field

C. A key that uniquely identifies a tuple

D. A set of tuples in the table

Solution

1. Step 1: Define attribute in the context of a relation

   An attribute is a column in a table that describes a data field.

2. Step 2: Eliminate other options

   Rows are tuples, keys identify tuples, and sets of tuples form the relation, so only columns fit attribute.

3. Final Answer:

   A column representing a data field -> Option B

4. Quick Check:

   Attribute = column [OK]

Hint: Attribute means column in a table [OK]

Common Mistakes:

• Confusing attribute with tuple (row)
• Thinking attribute is a key
• Mixing attribute with entire relation

3. Consider a relation with attributes (ID, Name, Age) and tuples:
(1, 'Alice', 30), (2, 'Bob', 25), (3, 'Carol', 27)
How many tuples and attributes does this relation have?

medium

A. 2 tuples and 3 attributes

B. 3 tuples and 2 attributes

C. 2 tuples and 2 attributes

D. 3 tuples and 3 attributes

Solution

1. Step 1: Count the tuples (rows)

   There are three tuples: (1, 'Alice', 30), (2, 'Bob', 25), and (3, 'Carol', 27).

2. Step 2: Count the attributes (columns)

   Attributes are ID, Name, and Age, so there are three attributes.

3. Final Answer:

   3 tuples and 3 attributes -> Option D

4. Quick Check:

   Tuples = 3, Attributes = 3 [OK]

Hint: Count rows for tuples, columns for attributes [OK]

Common Mistakes:

• Counting attributes as tuples
• Ignoring one tuple or attribute
• Mixing up rows and columns

4. Identify the error in this relation definition:
Relation: Students(ID, Name, Age)
Tuples: (1, 'John'), (2, 'Jane', 22)

medium

A. Tuples have inconsistent number of attributes

B. Relation name is invalid

C. Attributes should be tuples

D. Tuples must be unique

Solution

1. Step 1: Check tuple lengths against attributes

   The relation has 3 attributes, but the first tuple has only 2 values.

2. Step 2: Confirm consistency requirement

   All tuples must have the same number of values as attributes; inconsistency is an error.

3. Final Answer:

   Tuples have inconsistent number of attributes -> Option A

4. Quick Check:

   Tuple length must match attributes [OK]

Hint: All tuples must match attribute count [OK]

Common Mistakes:

• Ignoring tuple length mismatch
• Thinking relation name is wrong
• Confusing uniqueness with attribute count

5. You have a relation Employees(EmpID, Dept, Salary) with tuples:
(101, 'HR', 5000), (102, 'IT', 6000), (103, 'HR', 5500)
How would you describe the attribute Dept in terms of its role in the relation?

hard

A. It is an attribute representing the department column

B. It is a tuple representing employee data

C. It is a key uniquely identifying each employee

D. It is a relation containing employee records

Solution

1. Step 1: Identify what Dept represents

   Dept is one of the columns describing employee data, so it is an attribute.

2. Step 2: Differentiate from tuples and keys

   Tuples are rows, keys uniquely identify tuples, and relation is the whole table, so Dept is an attribute.

3. Final Answer:

   It is an attribute representing the department column -> Option A

4. Quick Check:

   Dept = attribute (column) [OK]

Hint: Attributes are columns describing data fields [OK]

Common Mistakes:

• Confusing attribute with tuple (row)
• Thinking Dept is a key
• Mixing attribute with relation