Rails STI子类添加字段问题：基于Devise User父类的账户扩展

Hey there! Let's work through getting your STI setup with Devise sorted out, fixing that team_name field issue, and setting up the association between Participant and Mentor. Here's a step-by-step breakdown:

First off, STI relies on a type column in your parent users table to distinguish between Participant and Mentor. If you haven't added it yet, generate and run this migration:

rails generate migration AddTypeToUsers type:string
rails db:migrate

Then set up your models like this:

# app/models/user.rb
class User < ApplicationRecord
  devise :database_authenticatable, :registerable,
         :recoverable, :rememberable, :validatable
end

# app/models/participant.rb
class Participant < User
  # We'll add the association and validations here shortly
end

# app/models/mentor.rb
class Mentor < User
  # Association coming up too
end

Remember with STI, all fields live in the parent users table—you don't create separate tables for Participant or Mentor. To add team_name, generate a migration that adds it to the users table:

rails generate migration AddTeamNameToUsers team_name:string
rails db:migrate

Now you can add validation to the Participant model to ensure the field is present only for participants:

# app/models/participant.rb
class Participant < User
  validates :team_name, presence: true, if: -> { type == 'Participant' }
end

Since both are subclasses of User, we need to explicitly define the association details to avoid confusion for Rails. First, add a mentor_id foreign key to the users table:

rails generate migration AddMentorIdToUsers mentor_id:bigint
rails db:migrate

Then update your models to link them:

# app/models/participant.rb
class Participant < User
  validates :team_name, presence: true, if: -> { type == 'Participant' }
  belongs_to :mentor, class_name: 'Mentor', foreign_key: 'mentor_id', optional: true
  # Use `optional: true` if participants can exist without a mentor; remove it if they must have one
end

# app/models/mentor.rb
class Mentor < User
  has_many :participants, foreign_key: 'mentor_id'
end

• Forgot the type column: This is non-negotiable for STI—without it, Rails can't tell which subclass a user belongs to.
• Trying to create tables for subclasses: STI is single-table inheritance, so all data stays in the users table. Your Participant and Mentor models don't need their own database tables.
• Missing class_name in associations: Since both are User subclasses, Rails might guess the wrong model if you don't specify class_name: 'Mentor'.
• Not running migrations: Always run rails db:migrate after generating a migration—your database won't update otherwise!

Verify everything works by firing up rails console and running these commands:

# Create a mentor
mentor = Mentor.create(email: 'mentor@example.com', password: 'securepass123')

# Create a participant linked to the mentor
participant = Participant.create(
  email: 'participant@example.com',
  password: 'securepass123',
  team_name: 'Code Warriors',
  mentor_id: mentor.id
)

# Check the association
mentor.participants # Should return the participant we just created
participant.mentor # Should return the mentor

# Verify team_name is present
participant.team_name # => "Code Warriors"

内容的提问来源于stack exchange，提问作者wencakisa