View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009541 | mantisbt | db mssql | public | 2008-08-14 12:54 | 2015-03-15 19:58 |
Reporter | ReynoldTucan | Assigned To | dregad | ||
Priority | normal | Severity | block | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | Windows, PHP, MS SQL | OS | Windows XP | ||
Product Version | 1.1.2 | ||||
Target Version | 1.3.0-beta.2 | Fixed in Version | 1.3.0-beta.2 | ||
Summary | 0009541: Installation with MS SQL and odbc (odbc_mssql) | ||||
Description | The standard option of selecting 'mssql' in config_inc.php or config_defaults_inc.php would not work for me. However, using a connection string as the host and setting the db type to 'odbc_mssql' would allow the tests to pass on "check.php". Example: $g_db_type = 'odbc_mssql'; When attempting to install via "install.php", I could not get the installation to work using the MS SQL option in the drop down list. I suspected that it was because of the same reason described above - I needed to use odbc. So, as a quick fix I altered all of the lines reading "$g_db = ADONewConnection($f_db_type);" in "install.php" as shown below: #$g_db = ADONewConnection($f_db_type); #comment this line out Obviously this hardcoded solution is not ideal for a generic release, but it worked in my instance and now Mantis is up and running great. I would suggest in the next release to add an ODBC MS SQL option to the drop down list of databases on the "install.php" page. This might make things easier for people in my situation. Especially if they have limited php knowledge and can't fix the file for themselves. | ||||
Tags | No tags attached. | ||||
Hello, I've just had an attempt at fixing a number of odbc_mssql issues in the latest development trunk (aka 1.2.x)
These have been commented out as we've made possible values for custom fields as type X: ADODB doesn't allow 'type X' to be not null or have default values as some db's may not support it for some blob types - so far i'm not aware of any issues, and the behaviour of silently dropping DEFAULT/NOTNULL for blobs breaks updates for mssql.
|
|
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. |
|