Database table naming conventions in Ruby on Rails - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to name a table for storing user data following Rails conventions.

Ruby on Rails

create_table :[1] do |t|
  t.string :name
  t.timestamps
end

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

Ausers

Buser

CUser

Duser_data

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular form like 'user' instead of plural 'users'.

Using camel case like 'User' instead of lowercase.

Rails table names are plural and lowercase, so users is correct.

2fill in blank

medium

Complete the code to name a join table for users and roles in Rails.

Ruby on Rails

create_table :[1], id: false do |t|
  t.references :user
  t.references :role
end

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

Auser_role

Broles_users

Cuser_roles

Dusers_roles

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular or non-alphabetical order in join table names.

Adding extra words like 'user_role' instead of 'roles_users'.

Rails join tables are named by combining plural table names in alphabetical order, so roles_users is correct.

3fill in blank

hard

Fix the error in the table name to follow Rails conventions.

Ruby on Rails

create_table :[1] do |t|
  t.string :title
  t.timestamps
end

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

Abooks

Bbook

CBook

DBooks

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular or capitalized table names.

Not pluralizing the table name.

Rails expects table names to be lowercase and plural, so books is correct.

4fill in blank

hard

Fill both blanks to create a migration for a table named correctly and with a primary key.

Ruby on Rails

create_table :[1], [2] do |t|
  t.string :email
  t.timestamps
end

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

Acustomers

Bprimary_key: :id

Ccustomer

Did: false

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular table names.

Incorrect primary key options like 'id: false' when a primary key is needed.

The table name should be plural customers and the primary key option is primary_key: :id by default.

5fill in blank

hard

Fill all three blanks to define a join table with no id and correct naming.

Ruby on Rails

create_table :[1], [2] do |t|
  t.references :[3]
  t.references :group
end

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

Agroups_users

Bid: false

Cuser

Dusers_groups

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular or incorrectly ordered join table names.

Forgetting to disable the id column for join tables.

The join table name is groups_users (alphabetical plural), no id column with id: false, and references to user and group.

Practice

1. In Rails, what is the correct way to name a database table for storing multiple user records?

easy

A. users

B. User

C. userTable

D. UsersTable

Solution

1. Step 1: Understand Rails table naming convention

   Rails expects table names to be plural and lowercase to represent collections of records.

2. Step 2: Apply naming to the user entity

   The plural form of "user" is "users", all lowercase, matching Rails conventions.

3. Final Answer:

   users -> Option A

4. Quick Check:

   Plural lowercase table name = users [OK]

Hint: Table names are plural and lowercase with underscores [OK]

Common Mistakes:

• Using singular names like 'User'
• Capitalizing table names
• Adding extra words like 'Table'

2. Which of the following is the correct Rails table name for a model named OrderItem?

easy

A. OrderItems

B. orderitems

C. order_items

D. order-Items

Solution

1. Step 1: Identify word separation in table names

   Rails uses underscores to separate words in table names, all lowercase.

2. Step 2: Convert 'OrderItem' to table name

   Split words with underscore and pluralize: 'order_items'.

3. Final Answer:

   order_items -> Option C

4. Quick Check:

   Use underscores and plural lowercase = order_items [OK]

Hint: Use underscores between words, all lowercase [OK]

Common Mistakes:

• Writing names without underscores
• Using camel case or hyphens
• Capitalizing letters in table names

3. Given a Rails model named BlogPost, which table name will Rails expect to find in the database?

medium

A. blog_posts

B. blogposts

C. BlogPosts

D. blog-posts

Solution

1. Step 1: Recall Rails naming rules for tables

   Tables are plural, lowercase, and use underscores to separate words.

2. Step 2: Apply rules to 'BlogPost'

   Split words with underscore and pluralize: 'blog_posts'.

3. Final Answer:

   blog_posts -> Option A

4. Quick Check:

   Plural, lowercase, underscores = blog_posts [OK]

Hint: Pluralize and underscore multiword model names [OK]

Common Mistakes:

• Using camel case or hyphens
• Not pluralizing the table name
• Capitalizing table names

4. You have a table named user_profiles but your Rails model is named UserProfile. You get an error that the table does not exist. What is the likely cause?

medium

A. The table name should be singular: user_profile

B. The table name is correct; the error is elsewhere

C. The table name should be plural and lowercase with underscores, which it is

D. The table name should be camel case: UserProfiles

Solution

1. Step 1: Check Rails table naming conventions

   Rails expects plural, lowercase, underscore-separated table names matching the model name.

2. Step 2: Verify the table name 'user_profiles'

   This matches the convention for model 'UserProfile'. So the table name is correct.

3. Final Answer:

   The table name is correct; the error is elsewhere -> Option B

4. Quick Check:

   Table name matches Rails convention = user_profiles [OK]

Hint: Rails table names are plural lowercase with underscores [OK]

Common Mistakes:

• Changing table name to singular
• Using camel case for table names
• Assuming error is table name when it is not

5. You want to create a join table for a many-to-many relationship between Author and Book models in Rails. What is the correct table name?

hard

A. author_books

B. AuthorsBooks

C. author_book

D. authors_books

Solution

1. Step 1: Understand Rails join table naming

   Join tables are named by combining the plural names of both models in alphabetical order, separated by an underscore.

2. Step 2: Apply to 'Author' and 'Book'

   Plural forms are 'authors' and 'books'. Alphabetically, 'authors' comes before 'books', so the table name is 'authors_books'.

3. Final Answer:

   authors_books -> Option D

4. Quick Check:

   Join table = plural model names in alphabetical order [OK]

Hint: Join tables use plural model names alphabetically joined by underscore [OK]

Common Mistakes:

• Using singular names in join table
• Not ordering names alphabetically
• Capitalizing join table names