Oracle Database Type Mappings have changed
When data is read from/ written to the database, a LookupTable of Database data types -> Smalltalk classes is used to determine how data in a column is mapped.
Reason for change
In order to provide Oracle-specific type fixes, some existing Oracle type mapping methods have been changed from generic type mapping classes, to Oracle-specific subclasses.
Action required
If you use a manager subclassed from AbtOracle (8/10) DatabaseManager which implements buildTypeDict, or in some other way installs an expanded set of type mappings (by sending #typeDict:) - make sure to update your mappings to be consistent with the new classes, and move any custom extensions to the type class to the new Oracle-specific class.
The mappings that changed class, were:
o Oci_Varchar2_Datatype: AbtDatabaseVarCharField -> AbtOracleVarCharField
o Oci_Varchar_Datatype: AbtDatabaseVarCharField -> AbtOracleVarCharField
o Oci_Rowid_Datatype: AbtDatabaseVarCharField -> AbtOracleVarCharField
o Oci_Char_Datatype: AbtDatabaseVarCharField -> AbtOracleVarCharField
If you leave the old mapping classes in your type dictionary, you will experience failures when trying to read from/write to fields of the changed types.
Last modified date: 03/04/2025