(PG::UndefinedColumn: ERROR when calling current_user.games - ruby-on-rails

Question

I'm trying to call current_user.games and keep getting the error:
ActiveRecord::StatementInvalid (PG::UndefinedColumn: ERROR: column assignments.user_id does not exist)
LINE 1: ..." ON "games"."id" = "assignments"."game_id" WHERE "assignmen...
I believe my models are set up right to handle such a query but something tells me I have to run a migration that adds users as a reference?
Models:
class User < ApplicationRecord
devise :invitable, :database_authenticatable, :registerable,
:recoverable, :rememberable, :validatable, :invitable, invite_for: 2.weeks
has_many :assignments
has_many :games, through: :assignments
end
class Game < ApplicationRecord
has_one :assignment, dependent: :destroy
has_many :users, through: :assignment
after_save :create_assignment
def create_assignment
Assignment.create(game_id: id)
end
end
class Assignment < ApplicationRecord
belongs_to :game
belongs_to :user
# belongs_to :assignor, class_name: "User", optional: true
belongs_to :center_referee, class_name: 'User', optional: true
belongs_to :assistant_referee_1, class_name: 'User', optional: true
belongs_to :assistant_referee_2, class_name: 'User', optional: true
accepts_nested_attributes_for :game
end
Schema:
create_table "assignments", force: :cascade do |t|
t.integer "game_id"
t.integer "center_referee_id"
t.integer "assistant_referee_1_id"
t.integer "assistant_referee_2_id"
t.datetime "created_at", precision: 6, null: false
t.datetime "updated_at", precision: 6, null: false
end
create_table "games", force: :cascade do |t|
t.string "home_team"
t.string "away_team"
t.datetime "created_at", precision: 6, null: false
t.datetime "updated_at", precision: 6, null: false
end
create_table "users", force: :cascade do |t|
t.string "email", default: "", null: false
t.string "encrypted_password", default: "", null: false
t.string "reset_password_token"
t.datetime "reset_password_sent_at"
t.datetime "remember_created_at"
t.integer "sign_in_count", default: 0, null: false
t.datetime "current_sign_in_at"
t.datetime "last_sign_in_at"
t.string "current_sign_in_ip"
t.string "last_sign_in_ip"
t.datetime "created_at", precision: 6, null: false
t.datetime "updated_at", precision: 6, null: false
t.string "first_name"
t.string "last_name"
t.string "role"
end

Answer 1

Short answer: you won't achieve what you are trying to using has_many. At least not the way your table is designed. You should try using scope instead, unfortunately.
On the other hand, there is a different way to design your system. See the new Assignment. Schema:
create_table "assignments", force: :cascade do |t|
t.integer "game_id"
t.integer "user_id"
end
Models:
class Assignment < ApplicationRecord
belongs_to :game
belongs_to :user
end
class User < ApplicationRecord
has_many :assignments
has_many :games, through: :assignments
end
class Game < ApplicationRecord
has_many :assignments
has_many :users, through: :assignments
end
You may wanna differ a center referee from an assistant referee.
I don't know exactly what your role column at the User model means, so I will assume your role column has nothing to do with center/assistant referee.
If this is the case, I'd add an unsigned tinyint role to Assignment and use it as enum. So my model would be:
class Assignment < ApplicationRecord
belongs_to :game
belongs_to :user
enum role: { center_referee: 0, assistant_referee_1: 1, assistant_referee_2: 2 }
# in case there must be only a kind of referee for a game:
validates(:role, uniqueness: { scope: [:game_id] })
end
And my Schema:
create_table "assignments", force: :cascade do |t|
t.integer "role", limit: 1, unsigned: true
t.integer "game_id"
t.integer "user_id"
end