View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020074 | mantisbt | db mssql | public | 2015-09-03 19:08 | 2016-01-25 16:21 |
Reporter | alex.volkov | Assigned To | dregad | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | Microsoft | OS | Windows Server 2012 R2 | ||
Product Version | 1.3.0-beta.2 | ||||
Fixed in Version | 1.3.0-rc.1 | ||||
Summary | 0020074: ADODB_FETCH_MODE global is not properly set by database_api.php | ||||
Description | database_api.php attempts to set ADODB_FETCH_MODE global (from adodb.inc.php) to ADODB_FETCH_ASSOC. But because require_lib() function is used to bring in the adodb.inc.php, the ADODB_FETCH_MODE is not brought in as a global into the scope. database_api.php does not declare ADODB_FETCH_MODE as a global either. This results in the following line creating a new ADODB_FETCH_MODE variable in the scope: The ultimate result is ADODB using the ADODB_FETCH_DEFAULT mode (0), which for mssqlnative driver appears to be ADODB_FETCH_NUM. The var should be declared global in database_api.php: | ||||
Additional Information | MS Windows Server 2012 R2 / IIS v8.5 Here is the failed trace: ADODB_Setup() called | ||||
Tags | No tags attached. | ||||
Thanks for the detailed bug report. |
|
I had already identified this issue in my ADOdb update branch, back in May 2015. This was actually fixed in 1.3.0-rc.1 (MantisBT master f0c3959b) |
|
MantisBT: master f0c3959b 2015-05-16 23:59 Details Diff |
Database API now properly sets ADOdb fetch mode Prior to this, the lack of global indicator for $ADODB_FETCH_MODE caused the driver to load with default setting, since the variable was initialized outside of its scope. |
Affected Issues 0020074 |
|
mod - core/database_api.php | Diff File |