PG::UndefinedTable: ERROR: relationship “done_statuses_for_project” does not exists
LINE 1: SELECT id FROM “statuses” INNER JOIN “done_statuses_for_proj…
^
: SELECT id FROM ”statuses" INNER JOIN “done_statuses_for_project” ON “statuses”.“id” = “done_statuses_for_project”.“status_id” WHERE “done_statuses_for_project”.“project_id” = 4 ORDER BY position ASC

Hi Max,

thanks for the second error msg. It looks like you have to run the migrations again.

Go to your OpenProject root folder and run the following:

RAILS_ENV=production bundle exec rake db:migrate

Best
Ratzi

And also entering Project BackLog

: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod
FROM pg_attribute a LEFT JOIN pg_attrdef d
ON a.attrelid = d.adrelid AND a.attnum = d.adnum
WHERE a.attrelid = ‘“export_card_configurations”’::regclass
AND a.attnum > 0 AND NOT a.attisdropped
ORDER BY a.attnum

do you suggest me change db?
how to check if database has the correct ‘schema’ ?

Thank you.
Max

Hello again,

you don’t have to change the database.
Usually you get an error like this PG::UndefinedTable: ERROR: relationship "done_statuses_for_project" does not exists if you have missing database migrations. Some plugins, like backlogs, adding new tables or columns to the database with Rails migrations.
With the suggested command you run this migrations and the missing tables and columns will be added to the database.

If you run OpenProject in development mode you should use this command instead of the other (was for production environment)?

bundle exec rake db:migrate

Best
Ratzi

Solved,
thank you very much.
Max

Christian Ratz wrote:

Hi Max,

thanks for the second error msg. It looks like you have to run the migrations again.

Go to your OpenProject root folder and run the following:

[…]

Best
Ratzi

Hi,

just one clarification: Is it safe to run bundle exec rake db:migrate even there are no updates to the DB?

For example, I would like to be sure that I have applied db:migrate and I accidentally run it 2 times. Is it safe?

Many thanks,
Igor

Hello Igor,

you can run ‘db:migrate’ as often as you like. Rails use the timestamps of the migrations to identify them so a migration run only once except you re run the migration by hand.

Best
Ratzi