Table 5 lists the issues that were fixed for ECDA Option for ODBC.
Target DBMS |
Description |
Resolution |
QTS # |
|---|---|---|---|
All |
Incorrect date formatting occurred with only 3-digit years. |
Dates are correctly formatted with all 4 digits. |
421328 |
Column names containing “$” were not correctly SQL transformed. |
SQL transformation now supports “$” in column names. |
417800 |
|
Microsoft SQL Server |
WCHAR columns caused a failure in sp_columns. |
WCHAR columns are now supported in sp_columns. |
417657 |
ReturnNativeError = yes returned an error message instead of a Microsoft SQL error message. |
ReturnNativeError = yes now returns a Microsoft SQL error message. |
404658 |
|
Null text column result failed when tracing was set to “on.” |
The method of sending null result value was changed. |
401899 |
|
The NTEXT datatype mapped incorrectly through ASE/CIS. |
sp_columns was adjusted for NTEXT datatype and XNL settings. |
392089 |
|
A conflicting datatype was returned in sp_columns when mapping Unicode to text. |
The problem in sp_columns was fixed for both cspcolumnODBCVersion = 2 and 3. |
354091 |
|
A null character data caused a SQL statement truncation. |
Null characters and binary zeros in SQL statement are now stripped when the StripBinaryZero property is set. |
291774 |
|
DB2 UDB |
The sp_who stored procedure caused a segmentation fault. |
Result handling was corrected to allow zero row result set for DB2 targets. |
420094 |
SQL statements containing SUBSTRING would not change or be transformed to SUBSTR. |
SUBSTR is now used for DB2 targets. |
402619 |
|
The ASE or CIS cursor date parameter was bound as a datetime datatype on DB2. |
The date datatype parameter is now bound as a date datatype. |
402362 |
