RWDBDateTime
RWDBDateTime is deprecated and where possible it has been replaced by RWDateTime in the SourcePro DB API.
While RWDBDateTime and RWDateTime provide constructors and operators to allow implicit conversion between the two types, there may still be instances where the switch from RWDBDateTime to RWDateTime will cause compilation failures in your code. Normally this would occur in code that is counting on an implicit conversion from RWDBDateTime to some other type. In those cases, you will either need to update your code to use RWDateTime instead, or you will need to explicitly cast the result of a function to an RWDBDateTime.
Oracle Stored Procedures
The Access Module for DB2 CLI uses the table name supplied by the user to retrieve the schema associated with that table. Previously it attempted to qualify/unqualify the name if the schema could not be retrieved using the original name, but this sometimes resulted in returning the schema for the wrong table so this behavior has been removed.
If your code depends on the previous fallback behavior you will need to update your code to explicitly look up the table schema using an unqualified name if the lookup with a qualified name fails.
Dependency on maxStringSize() and maxBlobSize()
Previously both of these were checked for a result column, but now only one or the other will be checked based on the result column type.
If your code currently depends on either maxBlobSize() or maxStringSize(), but not both, you may need to set both values if the value needs to be applied to both binary and character data.
Dependency on maxStringSize() and maxBlobSize()
Previously both of these were checked for a result column, but now only one or the other will be checked based on the result column type.
If your code currently depends on either maxBlobSize() or maxStringSize(), but not both, you may need to set both values if the value needs to be applied to both binary and character data.
Dependency on maxStringSize() and maxBlobSize()
Previously both of these were checked for a result column, but now only one or the other will be checked based on the result column type.
If your code currently depends on either maxBlobSize() or maxStringSize(), but not both, you may need to set both values if the value needs to be applied to both binary and character data.
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.