Differentiate between the terms Attribute and Domain in the context of Relational Data Model.

Question 22 of 29

Q. Differentiate between the terms Attribute and Domain in the context of Relational Data Model.

Yanam BieapCBSE Class XII Board 2022Subjective· 2mImportance★★★★★

76% · 22/29 Questions

🔒 Locked · start free trial →

You're viewing a preview — the full solution, concept, methods & PYQ mapping are locked.

Start your 14-day free trial to unlock the full solution →

Concept understanding — Database Schema

Database Schema: The Blueprint of a Database

Imagine you are organising a large library. You don't just pile books randomly. First, you decide: What information will we keep about each book? Title, author, ISBN, shelf number. Then you decide: How are these pieces of information related? A book has one shelf, but a shelf holds many books. You also decide rules: Every book must have an ISBN; no two books can share the same ISBN.

That plan — the structure you design before you put a single book on the shelf — is the schema.

The Precise Meaning

A database schema is the formal, logical description of how data is organised in a database. It defines:

What tables exist (like "Books", "Members", "Loans")
What columns each table has (e.g., BookID, Title, Author, YearPublished)
What type of data each column holds (text, number, date, etc.)
What rules or constraints apply (e.g., "Every loan must refer to an existing member")
How tables relate to one another (e.g., "A member can borrow many books, but each loan record belongs to one member")

Think of the schema as the skeleton of the database. The actual data — the rows you fill in later — is the flesh and blood. The schema stays mostly unchanged; the data changes constantly.

Note

A common confusion: people say "the database" when they mean the data inside it. But the schema is the structure, not the data. Two databases can have the same schema but completely different data — like two schools using the same student record form but with different students' names.

Why the Schema Matters

Without a schema, data becomes a mess. You might store a customer's phone number in the "Name" column, or lose track of which orders belong to which customer. The schema prevents this by enforcing consistency and integrity.

Consider a bank. The schema says: "Every transaction must have an amount, a date, and a valid account number." If someone tries to enter a transaction without an account number, the database refuses — because the schema says so. This is not a software bug; it is a deliberate design choice built into the structure.

Key Components of a Schema

Tables – The main containers. Each table represents one kind of thing (Students, Products, Invoices).
Columns (Fields) – The attributes or properties of that thing (StudentName, DateOfBirth, Email).
Data Types – What kind of value each column holds (text, whole number, decimal, date).
Constraints – Rules that data must obey:
- Primary Key – A unique identifier for each row (like a roll number). No two rows can share it.
- Foreign Key – A column that links to another table's primary key, creating a relationship.
- Not Null – A column that must always have a value.
- Unique – A column where every value must be different.
Relationships – How tables connect: one-to-one, one-to-many, many-to-many. …

Start your 14-day free trial to unlock the full solution →

Concept: Relational schema terminology — an attribute is a column of a relation, while a domain is the set of permissible values for that column.

Reasoning:

An attribute names a property (e.g., Student_Age) and appears as a column heading in a table.
A domain defines the data type and value constraints for that attribute (e.g., integers from 1 to 120). Multiple attributes can share the same domain. …

Start your 14-day free trial to unlock the full solution →

An attribute is a column (property) of a relation, while a domain is the set of permissible values that an attribute can take — the attribute is the name, the domain is the allowed data type and range.

The Core Idea

Think of a relation (table) as a spreadsheet of facts. Each column has a name — that's the attribute. But every column also has a type of data it can hold: numbers, text, dates, etc. That type, along with any constraints on the values, is the domain. The attribute is what we're storing; the domain is how we constrain what can be stored there. This is a core idea in CBSE Class 12 Computer Science relational database concepts.

For example, in a Student table, you might have an attribute called age. The domain of age could be "integers between 1 and 120". The attribute is the label; the domain is the rulebook for valid entries.

Step-by-Step Breakdown

Attribute: The Column Name

An attribute is a named column of a relation. It represents a property or characteristic of the entity described by the relation.
- Example: In Student(roll_no, name, age), the attributes are roll_no, name, and age.
- Each attribute has a unique name within the relation schema.
Domain: The Set of Allowed Values

A domain is a set of atomic (indivisible) values from which one or more attributes draw their actual values. It defines the data type, length, and any constraints.
- Example: the domain of age could be all integers x such that 1 <= x <= 120.
- Domains are often shared across attributes — e.g., both student_age and teacher_age might use the same domain of "positive integers up to 120".
Key Difference: Name vs. Value Space

The attribute is the label; the domain is the pool of legal values.
- Two different attributes (e.g., age and years_of_experience) can share the same domain.
- An attribute cannot exist without a domain — every attribute must be defined over some domain.
Formal Definition in Relational Model

In Codd's relational model:
- A relation schema R(A1, A2, ..., An) has attributes A1 ... An.
- Each attribute Ai is associated with a domain Di.
- A tuple t in the relation assigns to each attribute Ai a value v such that v belongs to Di.

Tip

A neat way to remember: Attribute = column header, Domain = the "type" of that column (like INTEGER, VARCHAR(50), or a custom set like {'M','F'}). In SQL, the domain is essentially the data type plus any CHECK constraints.

Example to Cement the Idea Consider a relation Employee(emp_id, salary, gender).
- Attributes: emp_id, salary, gender.
- Domains:
  - emp_id: domain = 6-digit positive integers. …

Start your 14-day free trial to unlock the full solution →

←Previous questionQ7 — (A) (i) Define cartesian product with respect to RDBMS. (ii) Sunil wan…→Next questionQ9 — Consider the following SQL table MEMBER in a SQL Database CLUB: Table:…

Q.Differentiate between the terms Attribute and Domain in the context of Relational Data Model.

The Core Idea

Step-by-Step Breakdown

🎓Unlock everything free for 14 days

Unlock everything free for 14 days