Actions
Feature #7667
open
Hierarchy columns should not be nullables
Start date:
2011-02-21
Due date:
% Done:
0%
Estimated time:
Resolution:
Description
The root_id, lft, rgt columns of issues table, as well as lft and rgt of projects table should be defined as NOT NULL.
This could prevent users from running Redmine with corrupted data due to a wrong db migration by import/export.
Files
Related issues
Updated by Etienne Massip about 14 years ago
- Target version set to Candidate for next major release
Updated by Daniel Felix almost 13 years ago
Hi Etienne,
I just found this on the roadmap.
Any news on this issue? :-)
Updated by Etienne Massip almost 13 years ago
- Tracker changed from Defect to Feature
- Subject changed from Hierarchy columns should not be nullables. to Hierarchy columns should not be nullables
Still here
Updated by Go MAEDA almost 2 years ago
- File 0001-Add-not-null-constraints-to-lft-rgt-and-root_id-in-i.patch 0001-Add-not-null-constraints-to-lft-rgt-and-root_id-in-i.patch added
- File 0002-Add-not-null-constraints-to-lft-and-rgt-in-issues-ta.patch 0002-Add-not-null-constraints-to-lft-and-rgt-in-issues-ta.patch added
The attached patches add not null constraints to "root_id", "lft", and "rgt" columns in issues and projects tables.
Updated by Go MAEDA almost 2 years ago
- Target version changed from Candidate for next major release to 6.0.0
Updated by Marius BĂLTEANU about 1 year ago
- Target version changed from 6.0.0 to Candidate for next major release
Updated by Marius BĂLTEANU about 1 year ago
- Target version changed from Candidate for next major release to 6.1.0
Updated by Marius BĂLTEANU 2 months ago
- Target version changed from 6.1.0 to Candidate for next major release
Actions