View Issue Details

IDProjectCategoryView StatusLast Update
0026599mantisbtdb schemapublic2024-03-08 03:00
Reporterdregad Assigned Todregad  
PrioritynormalSeveritymajorReproducibilityN/A
Status closedResolutionno change required 
Summary0026599: Behavioural changes for BLOBs in ADOdb 5.21
Description

ADOdb library version 5.21.0 introduces changes in BLOB handling.

See obmsch's note 0026599:0063444 below.

TagsNo tags attached.

Relationships

child of 0028015 closeddregad Update ADOdb to 5.21.4 

Activities

dregad

dregad

2020-01-15 11:15

developer   ~0063440

As mentioned by @obmsch in 0026596:0063437

Difference in generated db schema with mssqlnative driver
custom_field.possible_values
5.20: [text] NULL
5.21: [text] NOT NULL, Default ''

obmsch

obmsch

2020-01-15 17:32

reporter   ~0063444

Additional information about the scope of the behavioural changes for BLOBs in ADOdb-5.21 for MantisBT:

1) Only 'X', 'X2', 'XL' and 'B' are affected.
2) The Oracle (oci8) driver 'datadict-oci8.inc.php' is not adjusted(yet).
3) No 'X2' in 'schema.php'.
4) The two 'B's in 'schema.php' (bug_file.content, project_file.content) should be Ok with 'mysql', 'mssql', 'postgres',
as [2] -> [203] and [29] -> [204] anticipate. But 'oci8'?
5) One 'X' in 'schema.php' (need to check).
6) 'XL' should be Ok with 'mysql', 'mssql', 'postgres' (not touched formerly, now handled equally). But 'oci8'?

@dregad This all boils down to [2,4,6] and [5]. No idea about this Oracle stuff, but that should be fixed before 5.21 is released.
I file an issue anyway.

dregad

dregad

2022-01-11 02:44

developer   ~0066159

Since this issue was basically a duplicate of 0028015 which is already used as a parent to track ADOdb 5.21 issues, I'm recycling this one to follow-up on BLOB-related stuff reported by @obmsch

dregad

dregad

2024-02-20 15:35

developer   ~0068575

This issue has been opened for over 3 years, MantisBT 2.26.0 was released in October 2023 with ADOdb 5.22.6 and no issues have been reported to date.

I'm therefore resolving this as no change required, considering that most of the (potential) issues are oci8-related, and I no longer have a working Oracle setup for testing anyway.