View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022063 | mantisbt | db mssql | public | 2016-12-22 08:54 | 2017-04-19 06:02 |
Reporter | obmsch | Assigned To | dregad | ||
Priority | normal | Severity | block | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.3.0-beta.1 | ||||
Target Version | 1.3.9 | Fixed in Version | 1.3.9 | ||
Summary | 0022063: Installation on MSSQL fails at step 209 | ||||
Description | The last step (209) of the installation is failing (might be related to 0021901). "user_id I UNSIGNED NOTNULL DEFAULT '0'" is the culprit here. The column is created in step 200 as "user_id I DEFAULT '0'" An index on that column is created in step 201; because of that index MSSQL doesn't allow the change to NOTNULL in 209. If I run the install with a modified schema ("I NOTNULL DEFAULT '0'" in step 200) all is Ok. | ||||
Additional Information | Initially reported by @obmsch in 0021883:0054518 | ||||
Tags | No tags attached. | ||||
We have the same problem with 2.0.0 stable version, so we can't install it on MSSQL. BAD |
|
@MDylan: Is this a new install or an upgrade from an earlier version? 1) New install 2) Upgrade |
|
@obmsch |
|
Considering that this blocks installation, for consistency, I'll backport this to 1.3.x (hence the change in target version) and apply it in supported 2.x releases as well. |
|
MantisBT: master 3a0706a1 2017-03-22 07:15 Committer: dregad Details Diff |
Modify schema to get install/upgrade work with db-mssql. Although the problem appears in step 209, the real cause is the combination of steps 200 and 201. The Index ('user_id','name') created in step 201 (with a nullable 'user_id' as of step 200) forbids the alteration of 'user_id' to NOTNULL in step 209, at least with mssql. So fix this in step 200 and set 'user_id' NOTNULL right from start. While this is a 'post release' change, it is justifiable as it happens in the same install/upgrade sequence and the final db (schema) is identical. Fixes 0022063 |
Affected Issues 0022063 |
|
mod - admin/schema.php | Diff File | ||
MantisBT: master-1.3.x 8decd714 2017-03-22 07:15 Committer: dregad Details Diff |
Modify schema to get install/upgrade work with db-mssql. Although the problem appears in step 209, the real cause is the combination of steps 200 and 201. The Index ('user_id','name') created in step 201 (with a nullable 'user_id' as of step 200) forbids the alteration of 'user_id' to NOTNULL in step 209, at least with mssql. So fix this in step 200 and set 'user_id' NOTNULL right from start. While this is a 'post release' change, it is justifiable as it happens in the same install/upgrade sequence and the final db (schema) is identical. Fixes 0022063 Signed-off-by: Damien Regad <dregad@mantisbt.org> Backported from master 3a0706a1bc291be6ee684bd30199bd6544f0cc6b |
Affected Issues 0022063 |
|
mod - admin/schema.php | Diff File | ||
MantisBT: master-2.1 5fec5fb9 2017-03-22 07:15 Committer: dregad Details Diff |
Modify schema to get install/upgrade work with db-mssql. Although the problem appears in step 209, the real cause is the combination of steps 200 and 201. The Index ('user_id','name') created in step 201 (with a nullable 'user_id' as of step 200) forbids the alteration of 'user_id' to NOTNULL in step 209, at least with mssql. So fix this in step 200 and set 'user_id' NOTNULL right from start. While this is a 'post release' change, it is justifiable as it happens in the same install/upgrade sequence and the final db (schema) is identical. Fixes 0022063 |
Affected Issues 0022063 |
|
mod - admin/schema.php | Diff File | ||
MantisBT: master-2.2 98a31d53 2017-03-22 07:15 Committer: dregad Details Diff |
Modify schema to get install/upgrade work with db-mssql. Although the problem appears in step 209, the real cause is the combination of steps 200 and 201. The Index ('user_id','name') created in step 201 (with a nullable 'user_id' as of step 200) forbids the alteration of 'user_id' to NOTNULL in step 209, at least with mssql. So fix this in step 200 and set 'user_id' NOTNULL right from start. While this is a 'post release' change, it is justifiable as it happens in the same install/upgrade sequence and the final db (schema) is identical. Fixes 0022063 |
Affected Issues 0022063 |
|
mod - admin/schema.php | Diff File |