View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010437 | mantisbt | change log | public | 2009-04-30 11:50 | 2015-03-16 18:51 |
Reporter | damien_b | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.1.7 | ||||
Target Version | 1.3.0-beta.1 | Fixed in Version | 1.3.0-beta.1 | ||
Summary | 0010437: APPLICATION WARNING #403: Database field "description" not found. | ||||
Description | On Mantis 1.1.7 with an Oracle database (and at least up to 1.1.2), when going to changelog_page.php, the message | ||||
Tags | No tags attached. | ||||
This sounds more like an issue with ADOdb's handling of Oracle. Could you please try testing against the latest nightly builds [1] for 1.2.x? It includes a newer release of ADOdb, and would be nice to report any issues with it. Thanks |
|
It's not really an issue with ADOdb: the field is present in the array, associated to a NULL value, which is the correct semantic. On the other hand, testing for the presence of a key inside an array with isset is not semantically correct. |
|
Reminder sent to: grangeway Paul, since you're the database guy, can you take a look into this? Cheers. |
|
Same problem in custom_function_default_print_column_value: The test is wrong, it must be: |
|
MantisBT: master 2ce60e47 2011-08-10 08:34 Details Diff |
Fix 0013227: Oracle database support (oci8) Mantis 1.2.6 currently does not work with Oracle DB: 1. Installation: 1.1. Oracle DB autocreates PK, so index creation for same field forbidden 1.2. Oracle DB uses datetime literal format timestamp'YYYY-MM-DD HH-MI:SS' 1.3. Oracle DB don't allows altering field property NOT NULL into NOT NULL 1.4. Oracle DB max object length is 30 chars, so some index names must be reduced 1.5. Oracle DB means empty string as NULLs, so NOT NULL restriction must be disabled for some field 1.6. Oracle DB can resolve database server name through TNS, so database name cannot be required 2. General: 2.2. Direct DB query execution result accessing instead of db_fetch_array() 1.3. usage didn't works with Oracle DB 2.4. Oracle DB binds variable by name, so bind names in statement must be sorted to address them. 2.5. Oracle DB handles NULL/DEFAULT values with specific way. 2.6. Oracle DB returns NULL value as true PHP null 2.7. Oracle DB handles sequence access with specific syntax 2.8. Nothing returned by db_prepare_string() in case of oci8 2.9. Oracle DB max object length is 30 chars, so table names must be reduced 2.10. Oracle DB uses LOB literal format similar to mssql 2.11. GetRowAssoc returns empty field values with oci8, it's need to enable returning both associative and indexed arrays. The original patch was provided by DKuranov. He reckons that this also resolves issues 0006853, 0007644, 0010437, 0010996, 0011265, 0011270, 0011276, 0012152, 0012478 Porting to 1.3 - Conflicts: admin/install.php admin/schema.php core/database_api.php manage_tags_page.php |
Affected Issues 0006853, 0007644, 0010437, 0010996, 0011265, 0011270, 0011276, 0012152, 0012478, 0013227 |
|
mod - admin/install.php | Diff File | ||
mod - admin/schema.php | Diff File | ||
mod - core/database_api.php | Diff File |