Project

General

Profile

Actions

Defect #996

closed

CVS view ends up with "duplicate key violates unique constraint" after 0.7.0RC1 update

Added by Stefan Kremer about 16 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Toshi MARUYAMA
Category:
SCM
Target version:
-
Start date:
2008-04-04
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

This error first time came up after 0.7.0RC1 migration. SVN repository works fine. Only CVS repositories are affected.

Processing RepositoriesController#show (for 172.22.150.25 at 2008-04-02 17:31:40) [GET]
Session ID: e6ad346ab116a5d1e4df25d930061c49
Parameters: {"action"=>"show", "id"=>"project", "controller"=>"repositories"}

ActiveRecord::StatementInvalid (PGError: ERROR: duplicate key violates unique constraint "changesets_repos_rev"
: UPDATE changesets SET "scmid" = NULL, "comments" = E'no message', "commit_date" = '2007-12-03', "committer" = E'USER', "committed_on" = '2007-12-03 00:00:00.000000', "repository_id" = 5, "revision" = 1 WHERE "id" = 14):

Version: 0.7.0RC1
Database: Postgre


Files

test.csv (533 Bytes) test.csv Query Result Stefan Kremer, 2008-04-08 13:20
repository2.csv (6.03 KB) repository2.csv Partial query result Sandrine LEAL, 2008-07-10 17:53

Related issues

Related to Redmine - Defect #3761: Most recent CVS revisions are missing in "revisions" viewClosedToshi MARUYAMA2009-08-19

Actions
Related to Redmine - Defect #6706: Resolving issues with the commit message produces the wrong comment with CVSClosedToshi MARUYAMA2010-10-20

Actions
Has duplicate Redmine - Defect #1098: Upgrading from 0.6.3 to 0.7 , get repsoitiory page info errorClosed2008-04-24

Actions
Actions

Also available in: Atom PDF