Defect #996
CVS view ends up with "duplicate key violates unique constraint" after 0.7.0RC1 update
| Status: | Closed | Start: | 2008-04-04 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | SCM | |||
| Target version: | 0.7 | |||
| Affected version: | 0.7.0-RC1 |
Resolution: | ||
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
Related issues
| duplicated by Defect #1098 | Upgrading from 0.6.3 to 0.7 , get repsoitiory page info error | Closed | 2008-04-24 |
Associated revisions
History
2008-04-04 13:45 - Jean-Philippe Lang
Is it a new CVS repository or is it a repository that was already loaded before the migration to 0.7RC1 ?
2008-04-04 15:32 - Stefan Kremer
Hi Jean-Philippe,
THX for your fast answer. All repositories are created before migration.
2008-04-04 18:31 - Jean-Philippe Lang
I don't have a clue.
Could you post (as attached file) the result of this query:
select id, revision, committed_on from changesets where repository_id = 5
Thanks
2008-04-08 09:22 - Stefan Kremer
BTW. We got three CVS all of them do not work since updated to 0.7.0 RC1.
2008-04-13 12:12 - Jean-Philippe Lang
- Category set to SCM
I can't see what is happening. I've imported a CSV repository in a 0.6.4 install with a postgresql DB then migrated to 0.7.0RC1 and everything works as expected. New CVS commits are properly added to the database.
Could you post the error log so I can see exactly where this error comes from ?
2008-04-24 19:30 - Jean-Philippe Lang
- Status changed from New to Resolved
- Target version set to 0.7
r1355 should fix this problem. Can you confirm please ?