Following are issues relating to DirectConnect for Oracle.
If the default character set for DirectConnect for Oracle does not match that of ASE/CIS, and a writetext is issued to insert text, the text field is not converted as expected. For the us_english language, this should not be a problem, as the normal printing characters are the same in the supported character sets. For other languages, this can pose a problem.
The workaround is to make sure that ASE/CIS has the same default character set as DirectConnect for Oracle. For better performance, it is always best to use the same character set.
Joins between char columns and varchar columns might not return any rows. In addition, the query returns no rows when run directly against Oracle using SQLPLUS. However, running the query against Adaptive Server with the same data will return rows. The difference arises because Sybase and Oracle have different comparison rules when the columns are not all fixed length. The workaround is to alter the table definitions so the column definitions match.
If a column c1 of type char(5) has a value “a” inserted into it, the following SQL statement will not return any rows if the table is on an Oracle database:
select...where c1 like "a"
Blank-padded comparison is not done by Oracle for arguments to like clauses. When executed against a table on Adaptive Server, the same SQL statement fetches the row.
Given the same setup, the following SQL statement returns the row when the table is on either Adaptive Server or Oracle:
select...where c1 = "a"
When c1 = “a” is used, Oracle does blank-padded comparison.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
