Originally created by @ihudak on GitHub (Mar 10, 2017).
when doing migration (rails 4.2.7.1 and 4.2.8 on postgres db), rails interprets job_id as a reference to job table (which does not exist).
Changing the job_id string in the migration file:
t.string :job_id, null: false, foreign_key: false
(add foreign_key: false) solves the problem
Originally created by @ihudak on GitHub (Mar 10, 2017).
when doing migration (rails 4.2.7.1 and 4.2.8 on postgres db), rails interprets job_id as a reference to job table (which does not exist).
Changing the job_id string in the migration file:
t.string :job_id, null: false, foreign_key: false
(add foreign_key: false) solves the problem
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ihudak on GitHub (Mar 10, 2017).
when doing migration (rails 4.2.7.1 and 4.2.8 on postgres db), rails interprets job_id as a reference to job table (which does not exist).
Changing the job_id string in the migration file:
t.string :job_id, null: false, foreign_key: false
(add foreign_key: false) solves the problem