View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009315 | mantisbt | db mssql | public | 2008-06-30 05:47 | 2017-04-19 06:02 |
Reporter | LordLarry | Assigned To | dregad | ||
Priority | normal | Severity | block | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | Windows | OS | Windows Server | OS Version | 2003 |
Product Version | 1.2.0a1 | ||||
Target Version | 1.3.0-beta.2 | Fixed in Version | 1.3.0-beta.2 | ||
Summary | 0009315: admin/install.php fails because of wrong ALTER TABLE | ||||
Description | $upgrade[] = Array('AlterColumnSQL', Array( db_get_table( 'mantis_user_pref_table' ), "redirect_delay I NOTNULL DEFAULT 0" ) ); which results in ALTER TABLE mantis_user_pref_table ALTER COLUMN redirect_delay INT DEFAULT (0) NOT NULL The resulting query gives an error in MSSQL: Incorrect syntax near the keyword 'DEFAULT'. Something like this should work: ALTER TABLE mantis_user_pref_table ALTER COLUMN redirect_delay INT NOT NULL But I also get complaints about indexes not allowing the change. | ||||
Steps To Reproduce | Create a new MSSQL mantis database using admin/install.php | ||||
Tags | No tags attached. | ||||
ALTER TABLE mantis_custom_field_table ALTER COLUMN possible_values TEXT NULL; fails because of existing index when using MSSQL |
|
using MSSQL 2000 |
|
grangeway, are you able to reproduce this issue? |
|
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|
Please try this again using a nightly build of the master branch. |
|
Marking as Suspended MSSQL support is currently known broken. We are going to be replacing the DB Layer in Mantis to fix this properly after the next release. I'd strongly advise using MYSQL for now. The new DB layer already contains the appropriate fixes for MS SQL Support. |
|
MSSQL support is currently known broken. We are going to be replacing the DB Layer in Mantis to fix this properly after the next release. I'd strongly advise using MYSQL for now. The new DB layer already contains the appropriate fixes for MS SQL Support. |
|
MantisBT currently supports Mysql and has support for other database engines. The support for other databases is known to be problematic. Having implemented the current database layer into Mantis 10 years ago, I'm currently working on replacing the current layer. If you are interested in using Mantis with non-mysql databases - for example, Oracle, PGSQL or MSSQL, and would be willing to help out testing the new database layer, please drop me an email at paul@mantisforge.org In the meantime, I'd advise running Mantis with Mysql Only to avoid issues. Thanks |
|
Despite the fact that I am not actually able to test whether the problem is truly resolved since I don't have access to a MSSQL server setup, I'm marking this issue as fixed in 1.3.x on the grounds that the recent updates in ADOdb (which contain many improvements in the MSSQL driver) are likely to address it. Should the problem persist (using a nightly build or a version > 1.3.0-beta.1), feel free to reopen this issue or to create a new one. |
|