Redmine

Could you try to reuse the update SQL line in a postgresql terminal, please?

UPDATE issue_statuses SET position = (position - 1) WHERE (1 = 1 AND position > 8)

I'm rather sure that the problem is (position -1) where position should be already replaced by the old position value. Trying the exact line confirm that Postgresql can't reuse a referential value during an Update command.

Thank you.

No, the problem is not with that statement. If you check the log above you see that the error is with the next statement:

UPDATE issue_statuses SET "is_closed" = 'f', "name" = 'klklkl', "position" = NULL, "is_default" = 'f' WHERE "id" = 11

Just to confirm that:

redmine=# UPDATE issue_statuses SET position = (position - 1) WHERE (1 = 1 AND position > 8);
UPDATE 0
redmine=# UPDATE issue_statuses SET "is_closed" = 'f', "name" = 'klklkl', "position" = NULL, "is_default" = 'f' WHERE "id" = 11;
ERROR:  null value in column "position" violates not-null constraint
redmine=#

A bit more of info on this. The rake db:migrate command run without errors, and my schema is in the version 86 as expected:

 redmine=# SELECT * from schema_info ;
 version
---------
      86
(1 row)

So i think that migration 76 is not working properly with postgres. If we check table issue_statuses, we get:

 redmine=# \d issue_statuses
                                  Table "public.issue_statuses" 
   Column   |         Type          |                          Modifiers
------------+-----------------------+-------------------------------------------------------------
 id         | integer               | not null default nextval('issue_statuses_id_seq'::regclass)
 name       | character varying(30) | not null default ''::character varying
 is_closed  | boolean               | not null default false
 is_default | boolean               | not null default false
 position   | integer               | not null default 1
Indexes:
    "issue_statuses_pkey" PRIMARY KEY, btree (id)

I have the last version of the postgres adapter and I'm running PostgreSQL 8.2.4:

postgres (0.7.9.2008.01.28, 0.7.1)
    Ruby extension library providing an API to PostgreSQL

There was a bug on a few migrations. Some not null constraints were not removed with Postgresql.
This is fixed in r1140 and ported in 0.6 stable branch.

You can checkout the trunk or branches/0.6-stable, but you'll have to rerun the migration from your 0.5 database copy.
I hope you will enjoy the new features :-)

After further investigation, it seems as though the status initially named "Closed" (the name can be changed) cannot be deleted. I swapped names with a created status, and then I could delete it. Is it really necessary that this status needs to be special (i.e. cannot be deleted)?