View Issue Details

IDProjectCategoryView StatusLast Update
0014395mantisbtdb mssqlpublic2015-03-15 19:58
ReporterAlyndri Assigned Todregad  
PriorityhighSeveritycrashReproducibilityalways
Status closedResolutionfixed 
PlatformGoogle ChromeOSWinXPOS Version-
Product Version1.2.10 
Target Version1.3.0-beta.2Fixed in Version1.3.0-beta.2 
Summary0014395: Critical Failure when Assigning Tags to Multiple Issues at Once
Description

Database error after attaching tags to multiple issues from the 'view issues' page

Steps To Reproduce
  1. go to 'view issues' page

  2. select multiple issues

  3. choose 'attach tags' from dropdown box

  4. type in a tag and choose 'attach'

  5. select any issue (even one that has not had a tag attached)

  6. database error displayed (attached)

TagsNo tags attached.
Attached Files
tag error.JPG (30,937 bytes)   
tag error.JPG (30,937 bytes)   

Relationships

related to 0011744 closedrombert Failure getting tag candidates on MSSQL 
related to 0014441 acknowledged view.php - Tag Selection Dropdown only shows 'Exisiting Tags' but none of the actual tags in existence 

Activities

atrol

atrol

2012-06-19 02:31

developer   ~0032117

Do you use MSSQL databse?

Alyndri

Alyndri

2012-06-19 23:09

reporter   ~0032118

Hi Atrol, yes, this is implemented into MSSQL. is it a problem related to this?

atrol

atrol

2012-06-20 02:11

developer   ~0032119

this is implemented into MSSQL. is it a problem related to this?
I am quite sure it is because
a) I am not able to reproduce the issue using MySQL and
b) There have been similiar issues, see related 0011744

grangeway

grangeway

2014-02-17 13:26

reporter   ~0039445

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.

grangeway

grangeway

2014-03-27 19:12

reporter   ~0039757

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.

grangeway

grangeway

2014-05-16 15:00

reporter   ~0040328

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
Paul

dregad

dregad

2015-03-14 14:02

developer   ~0049230

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.