Model Meta class options in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the database table name for the model.

Django

class Product(models.Model):
    name = models.CharField(max_length=100)

    class Meta:
        db_table = [1]

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

A"products"

B"Product"

C"product_table"

D"productName"

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the table name

Using the model class name instead of a string

The db_table option sets the exact database table name. Here, "product_table" is the correct table name string.

2fill in blank

medium

Complete the code to order the model records by the 'created' field descending.

Django

class Article(models.Model):
    title = models.CharField(max_length=200)
    created = models.DateTimeField()

    class Meta:
        ordering = [[1]]

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

A"created"

B"-created"

C"+created"

D"created.desc"

Attempts:

3 left

💡 Hint

Common Mistakes

Using '+created' which is invalid

Using 'created.desc' which is not recognized

To order descending by a field, prefix the field name with a minus sign inside the ordering list.

3fill in blank

hard

Fix the error in the Meta class to make the model abstract.

Django

class BaseModel(models.Model):
    created = models.DateTimeField(auto_now_add=True)

    class Meta:
        [1] = True

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

Aabstract

Babstract_model

Cis_abstract

Dabstract_base

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect option names like 'abstract_model'

Forgetting to set it to True

The correct Meta option to make a model abstract is abstract = True.

4fill in blank

hard

Fill both blanks to set the verbose name and plural verbose name for the model.

Django

class Customer(models.Model):
    name = models.CharField(max_length=100)

    class Meta:
        verbose_name = [1]
        verbose_name_plural = [2]

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

A"client"

B"clients"

C"customer"

D"customers"

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping singular and plural values

Using incorrect strings that don't match the model meaning

verbose_name is the singular name, and verbose_name_plural is the plural form used in admin and elsewhere.

5fill in blank

hard

Fill all three blanks to create a unique constraint on 'email' and 'username' fields with a custom name.

Django

class UserProfile(models.Model):
    email = models.EmailField()
    username = models.CharField(max_length=50)

    class Meta:
        constraints = [
            models.UniqueConstraint(fields=[[1], [2]], name=[3])
        ]

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

A"email"

B"username"

C"unique_email_username"

D"user_unique"

Attempts:

3 left

💡 Hint

Common Mistakes

Using field names without quotes

Using an invalid constraint name

The UniqueConstraint requires a list of field names and a name string for the constraint.

Practice

1. What is the purpose of the Meta class inside a Django model?

easy

A. To create database indexes manually

B. To define the fields of the model

C. To write methods for the model

D. To customize model behavior like ordering and table name

Solution

1. Step 1: Understand the role of Meta class

   The Meta class is used inside a Django model to customize how Django treats the model behind the scenes, such as ordering and table naming.

2. Step 2: Differentiate from other model parts

   Fields define data, methods add behavior, and indexes are usually defined in Meta but not manually created there. Meta is mainly for options, not fields or methods.

3. Final Answer:

   To customize model behavior like ordering and table name -> Option D

4. Quick Check:

   Meta class = customize model behavior [OK]

Hint: Meta class customizes model options, not fields or methods [OK]

Common Mistakes:

• Confusing Meta with field definitions
• Thinking Meta defines methods
• Assuming Meta creates database indexes manually

2. Which of the following is the correct way to specify the database table name for a Django model using the Meta class?

easy

A. class Meta: db_table = 'my_table'

B. class Meta: table_name = 'my_table'

C. class Meta: database_table = 'my_table'

D. class Meta: table = 'my_table'

Solution

1. Step 1: Recall the correct Meta option for table name

   The correct Meta option to set the database table name is db_table.

2. Step 2: Check each option's syntax

   Only db_table is valid; others like table_name, database_table, and table are not recognized by Django.

3. Final Answer:

   class Meta: db_table = 'my_table' -> Option A

4. Quick Check:

   db_table sets table name [OK]

Hint: Use db_table to rename database table in Meta [OK]

Common Mistakes:

• Using incorrect attribute names like table_name
• Forgetting to indent inside Meta class
• Confusing Meta options with field options

3. Given this model snippet, what will be the default ordering of query results?

class Product(models.Model):
    name = models.CharField(max_length=100)
    price = models.DecimalField(max_digits=6, decimal_places=2)

    class Meta:
        ordering = ['-price', 'name']

medium

A. Products ordered by price descending, then name ascending

B. Products ordered by name descending, then price ascending

C. Products ordered by price ascending, then name ascending

D. Products ordered by name ascending only

Solution

1. Step 1: Understand the ordering list in Meta

   The ordering list ['-price', 'name'] means first order by price descending (because of the minus), then by name ascending.

2. Step 2: Interpret the ordering effect on query results

   Query results will show products with highest price first; if prices tie, they are sorted by name alphabetically.

3. Final Answer:

   Products ordered by price descending, then name ascending -> Option A

4. Quick Check:

   Ordering = ['-price', 'name'] means price desc, name asc [OK]

Hint: Minus sign means descending order in Meta ordering [OK]

Common Mistakes:

• Ignoring the minus sign for descending
• Assuming all ordering is ascending
• Mixing order of fields in ordering list

4. Identify the error in this Meta class definition:

class Meta:
    ordering = '-created_at'
    verbose_name = 'Blog Post'

medium

A. verbose_name must be a list, not a string

B. ordering should be a list or tuple, not a string

C. Meta class must be outside the model class

D. created_at field must be defined in Meta

Solution

1. Step 1: Check the type of ordering attribute

   The ordering option must be a list or tuple of field names, not a single string.

2. Step 2: Validate other Meta options

   verbose_name is correctly a string; Meta must be inside the model; fields are not defined in Meta.

3. Final Answer:

   ordering should be a list or tuple, not a string -> Option B

4. Quick Check:

   Ordering = list/tuple, not string [OK]

Hint: Ordering must be a list or tuple, never a plain string [OK]

Common Mistakes:

• Using string instead of list for ordering
• Placing Meta outside model class
• Confusing verbose_name type

5. You want to ensure your Django model Article has a unique combination of author and title. Which Meta option correctly enforces this at the database level?

hard

A. class Meta:\n unique_fields = ('author', 'title')

B. class Meta:\n unique = ['author', 'title']

C. class Meta:\n unique_together = ('author', 'title')

D. class Meta:\n unique_constraint = ('author', 'title')

Solution

1. Step 1: Recall the Meta option for composite uniqueness

   The correct Meta option to enforce uniqueness on multiple fields is unique_together.

2. Step 2: Verify syntax and alternatives

   Options like unique_fields, unique, and unique_constraint are not valid Django Meta options.

3. Final Answer:

   class Meta: unique_together = ('author', 'title') -> Option C

4. Quick Check:

   unique_together enforces multi-field uniqueness [OK]

Hint: Use unique_together tuple in Meta for multi-field uniqueness [OK]

Common Mistakes:

• Using invalid Meta option names
• Trying to enforce uniqueness outside Meta
• Confusing unique_together with unique=true on fields