Restrictions on the Use of Datatypes
Sybase Open Client Client-Library and Sybase Adaptive Server Enterprise place restrictions on the use of certain datatypes. Where possible, the DB Interface Module is flexible about datatypes. However, there are some situations where conversions are not possible, and in these cases your application must be aware of the contexts in which certain datatypes can be used. Table 3 outlines the restrictions associated with each DB Interface Module type.
Table 3 – Restrictions on the use of DB Interface Module datatypes
RWDBValue::ValueType
Restrictions
Char
UnsignedChar
No restrictions
String
WString
MBString
UString
Not supported on RWDBBoundExpr if string size is bigger than 16384 bytes
Blob
Not supported on RWDBBoundExpr
Short
UnsignedShort
No restrictions
Int
UnsignedInt
No restrictions
Long
UnsignedLong
No restrictions
Double
No restrictions
Float
No restrictions
Decimal
The precision and scale of a value can vary depending on the version of the Sybase client and server. Consistent versions of clients and servers can eliminate difficulties in conversions.
Date
No restrictions
DateTime
Supports dates ranging from January 1, 1753 through December 31, 9999, 23:59:59.999. However, accuracy is limited to 3.33 milliseconds by Sybase. Therefore, the maximum date that could be inserted is December 31, 9999, 23:59:59.996.
TimeTuple
No restrictions
TimeTupleOffset
Not supported
Duration
Not supported by the Sybase client
LongLong
UnsignedLongLong
Table creation not supported
LongDouble
No restrictions