Project

General

Profile

Actions

Defect #5099

closed

When deleting a project with children, the database seems to become corrupted

Added by Kioma Aldecoa about 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Projects
Target version:
-
Start date:
2010-03-17
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

After I deleted a project that contained children, issues of the projects of the affected rows showed up in the wrong project. I examined the database, and the lft and rgt columns of the project table in the database seemed to become corrupted. For some projects, the rgt value became less than the lft value. I was only able to fix this by manually editing the lft and rgt columns of the projects table.

Suggest making this a very high priority to fix if it is not already fixed -- this bug has the potential to show issues in the wrong project, which is a real security concern for those of us counting on redmine to keep issues contained in the correct projects.

Observed this in a recent 0.9-stable branch build, but not the latest, will try to determine exact build number and post here.


Related issues

Is duplicate of Redmine - Defect #4701: Project tree structure is broken by deleting the project with the subprojectClosed2010-01-31

Actions
Actions #1

Updated by Jean-Philippe Lang about 14 years ago

I think it's similar to #4701 which was fixed in r3354 then backported to 0.9-stable in r3381 (before 0.9.2 release).
Please let me know the Redmine revision you're using.

Actions #2

Updated by Kioma Aldecoa almost 14 years ago

This was in r3214.

Based on the description, this looks the same as #4701. If you want to close this bug as a duplicate, I can reopen if I see the problem after upgrading to a version after the fix for #4701.

Actions #3

Updated by Jean-Baptiste Barth over 13 years ago

  • Status changed from New to Closed
  • Affected version (unused) changed from devel to 0.9.1
  • Resolution set to Fixed
  • Affected version set to 0.9.1

Closing this one as suggested, you can reopen here or fill #4701 if it reappears with 0.9.6+.

Actions

Also available in: Atom PDF