View Issue Details

IDProjectCategoryView StatusLast Update
0015426mantisbtdb oraclepublic2014-12-08 00:34
Reporterdregad Assigned Todregad  
PrioritynormalSeverityblockReproducibilityalways
Status closedResolutionfixed 
Product Version1.2.12 
Target Version1.3.0-beta.1Fixed in Version1.3.0-beta.1 
Summary0015426: GetRowAssoc fails with Oracle DB
Description

With Oracle, calls to GetRowAssoc(0) fail to return data in the
associative array (all fields are set to null), even in 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.

TagsNo tags attached.

Relationships

related to 0009314 closeddregad ADODB GetRowAssoc does not work 
child of 0013227 closeddregad Oracle DB support multiple issues 

Activities

dregad

dregad

2013-01-25 10:38

developer   ~0034916

Last edited: 2013-01-25 12:23

I have submitted a patch [1] upstream [2]. Until this gets implemented, we work around the issue by setting ADODB_FETCH_MODE = ADODB_FETCH_NUM for Oracle in db_connect().

EDIT: this issue actually does NOT exist in the current Oracle branch, it was fixed in an earlier commit, setting fetch mode to ADODB_FETCH_BOTH; this will be replaced with ADODB_FETCH_NUM, which is more efficient (lower memory footprint).

Related Changesets

MantisBT: master 42152ec0

2013-01-28 04:06

dregad


Details Diff
Change ADOdb fetch mode to ADODB_FETCH_NUM for Oracle

We were previously using ADODB_FETCH_BOTH, which is less efficient as
each field is returned twice in the recordset. Using ADODB_FETCH_NUM
reduces the memory footprint.

This is a workaround for issue 0015426, allowing MantisBT to function
until ADOdb library is patched to fix the problem's root cause.
Affected Issues
0015426
mod - core/database_api.php Diff File

MantisBT: master 84d21a61

2014-05-12 23:23

dregad


Details Diff
oci8 no longer needs special fetch mode with ADOdb 5.19

Fixes 0015426
Affected Issues
0015426
mod - core/database_api.php Diff File