Relational Model: Tables, Rows, Columns, Domains

Active learning helps students grasp the relational model because abstract concepts like tables, rows, and domains become concrete when they physically organise and analyse data. By working with real-world examples, students see how databases structure information, making the model relevant and easier to remember.

• Class 12
• Computer Science
• 3 activities
• 15 min–25 min

Learning Objectives

1. Design a simple database table schema for a given real-world entity, specifying column names and appropriate data types (domains).
2. Compare and contrast the concepts of a record (row) and a field (column) within a relational database table.
3. Explain the role of domains in ensuring data integrity and consistency for specific attributes within a table.
4. Analyze a given dataset and classify its components into tables, rows, and columns based on the relational model.

Think-Pair-Share

⏱ 15 min·Pairs

Table Component Mapping

Provide a real-world entity like 'books'. Students map to table, rows, columns, domains. Share mappings.

Prepare & details

Explain how tables, rows, and columns represent data in a relational database.

Facilitation Tip: During Table Component Mapping, ask students to physically group related data points to reinforce the difference between records and fields.

Setup: Works in standard Indian classroom seating without moving furniture — students turn to the person beside or behind them for the pair phase. No rearrangement required. Suitable for fixed-bench government school classrooms and standard desk-and-chair CBSE and ICSE classrooms alike.

Materials: Printed or written TPS prompt card (one open-ended question per activity), Individual notebook or response slip for the think phase, Optional pair recording slip with 'We agree that...' and 'We disagree about...' boxes, Timer (mobile phone or board timer), Chalk or whiteboard space for capturing shared responses during the class share phase

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Think-Pair-Share

⏱ 25 min·Small Groups

Schema Construction Challenge

Design table for 'employees' with columns, data types. Include sample rows. Groups justify choices.

Prepare & details

Differentiate between a record and a field in a database table.

Facilitation Tip: While doing the Schema Construction Challenge, circulate and ask guiding questions like 'Which domain would you assign to this column, and why?' to deepen their reasoning.

Setup: Works in standard Indian classroom seating without moving furniture — students turn to the person beside or behind them for the pair phase. No rearrangement required. Suitable for fixed-bench government school classrooms and standard desk-and-chair CBSE and ICSE classrooms alike.

Materials: Printed or written TPS prompt card (one open-ended question per activity), Individual notebook or response slip for the think phase, Optional pair recording slip with 'We agree that...' and 'We disagree about...' boxes, Timer (mobile phone or board timer), Chalk or whiteboard space for capturing shared responses during the class share phase

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Think-Pair-Share

⏱ 20 min·Whole Class

Record vs Field Debate

List examples; students differentiate records and fields. Discuss domain importance.

Prepare & details

Construct a simple table schema for a given real-world entity, including data types/domains.

Facilitation Tip: In the Record vs Field Debate, encourage students to justify their answers with examples to clarify misconceptions on the spot.

Setup: Works in standard Indian classroom seating without moving furniture — students turn to the person beside or behind them for the pair phase. No rearrangement required. Suitable for fixed-bench government school classrooms and standard desk-and-chair CBSE and ICSE classrooms alike.

Materials: Printed or written TPS prompt card (one open-ended question per activity), Individual notebook or response slip for the think phase, Optional pair recording slip with 'We agree that...' and 'We disagree about...' boxes, Timer (mobile phone or board timer), Chalk or whiteboard space for capturing shared responses during the class share phase

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Teaching This Topic

Start with simple, relatable examples like student records or a school library database to build intuition. Avoid overwhelming students with jargon initially; let them discover the structure through guided activities. Research shows that hands-on practice with immediate feedback solidifies understanding better than lectures alone.

What to Expect

Students should confidently identify tables, rows, columns, and domains in any given dataset. They should also explain why domains matter and how they prevent errors in data entry. Look for clear articulation of these concepts during discussions and activities.

Watch Out for These Misconceptions

Common Misconception

During Table Component Mapping, watch for students who confuse rows and columns as interchangeable parts of a table.

What to Teach Instead

Use the activity’s data cards to ask: 'If this card represents a student’s record, what does each column tell us about the student? Now, how many such records (rows) do we have in total?'

Common Misconception

During Schema Construction Challenge, some students may assume domains are optional or irrelevant.

What to Teach Instead

Remind them to refer to the activity’s domain guidelines sheet and ask: 'What would happen if we stored a student’s age as a text instead of a number? How would that affect calculations or sorting?'

Assessment Ideas

Exit Ticket

After Table Component Mapping, provide a small table with employee data. Ask students to: 1. Count the number of records. 2. Name two fields. 3. Suggest a domain for the 'Department' field and explain why.

Quick Check

During Schema Construction Challenge, ask students to verbally share their table design with a partner. Listen for: the table name, 3-4 columns with their domains, and one example row (record).

Discussion Prompt

After Record vs Field Debate, initiate a class discussion: 'A student claims that rows and columns can be swapped in a table. How would you respond using the cricket team example we discussed? What rules (domains) would you set for each column to keep data clean?'

Extensions & Scaffolding

• Challenge early finishers to design a database for a local shop with at least 5 tables, including domains for each column.
• For students struggling, provide a partially completed table and ask them to fill in missing rows or suggest appropriate domains.
• Deeper exploration: Have students research how domains are implemented in real database software like MySQL or Oracle and compare their constraints.

Key Vocabulary

Table	A collection of related data entries organised in rows and columns. It represents a specific entity or concept, like 'Students' or 'Courses'.
Row (Record)	A single entry or data item within a table, representing a complete set of information for one instance of the entity. For example, one student's details in a 'Students' table.
Column (Field)	A vertical category within a table that represents a specific attribute or characteristic of the entity. For example, 'Name' or 'Roll Number' in a 'Students' table.
Domain	The set of permissible values or data types that a column can hold. It ensures data consistency, such as 'Integer' for age or 'String' for names.