View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009314 | mantisbt | db mssql | public | 2008-06-30 05:43 | 2014-12-08 00:34 |
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.1 | Fixed in Version | 1.3.0-beta.1 | ||
Summary | 0009314: ADODB GetRowAssoc does not work | ||||
Description | I have no idea why this does not work. Is it a php 5.2.6 problem? Or a bug in ADODB? Or something to do with MSSQL?
The wrong result is an array numberd from 0 to n-1 with no values changing | ||||
Steps To Reproduce | Just run mantis using a MSSQL database | ||||
Tags | adodb, patch | ||||
No problems with the same configuration in mantis 1.1.1 |
|
using MSSQL 2000 |
|
mmm, we are not upstream for ADODB but this looks like a bug in their code. Am I missing something or this should be reported upstream? |
|
I don't know. Just letting you know mantis does not work with the code it supplies |
|
If our code is not working, we are supposed to fix it. If other people code is not working, they should fix it. Assuming the GetRowAssoc() function is in the ADODB tree, this need to be reported (and fixed) upstream. Upstream is http://adodb.sourceforge.net/ and on that page you can see they want bug reports posted at http://phplens.com/lens/lensforum/topics.php?id=4 Please add here a link to your bug report so we can track the status of the issue, and update our code when they do a new release fixing this. |
|
I understand that. But I also understand that mantis won't work for MSSQL in the current state. That, I think, is also a problem for mantis. Reported here: http://phplens.com/lens/lensforum/msgs.php?id=17539 |
|
Yeah, that's why I'm not closing this straight away :) If you fancy helping further, it would be nice to test their latest release and see if they already solved the issue. |
|
Still no answer from the ADODB people |
|
Found same problem with Oracle. LordLarry's correction would not work as we need to change the case of the array keys, so I put a solution on the ticket LordLarry opened in ADODB. |
|
1.3.x will include a new PDO layer - so will not be affected by the adodb issue |
|
Reopened, the issue is not fixed in master branch (1.3.x) at the
|
|
Update from upstream http://phplens.com/lens/lensforum/msgs.php?id=17539 Topic: Re:ADODB GetRowAssoc does not work with MSSQL |
|
Fixed in AdoDB 5.17 |
|
GetRowAssoc is still an issue for Oracle even with latest version of AdoDB 5.18. This is due to MantisBT defaulting to ADODB_FETCH_ASSOC fetch mode, and the fact that Oracle returns uppercase column names in the recordset. I have submitted a patch [1] upstream [2]. Until this gets implemented, we can probably work around the issue by setting ADODB_FETCH_MODE = ADODB_FETCH_NUM for Oracle in db_connect(). [1] https://github.com/dregad/ADOdb/tree/fixes-518a |
|
Changed relation to 0013713 from parent/child to related, since there is a workaround possible by changing MantisBT code we don't need to set a hard dependency to have this issue fixed upstream (although we'd get better performance with the fix) Note - to-date, there is no sign of a new ADOdb release coming out, John Lim has been silent since end of 2012... |
|