Event Stream Processor datatypes map to Adaptive Server datatypes.
During message flow, the adapter verifies that incoming values can fit into the specified Adaptive Server Enterprise columns without losing precision, and rejects the rows if they cannot. The mappings that require runtime data checks are identified at adapter start-up, and only these mappings are verified for each record flowing through the adapter. Due to the performance impact of runtime checks on each record, Sybase recommends you do not use these mappings unless you cannot make changes to existing schemas.
There is no required precision or scale for float to numeric or decimal mapping during adapter initialization. However, during message flow, any rows which have an error occur while data is converting from Event Stream Processor float to Adaptive Server Enterprise numeric or decimal is rejected. This generally occurs due to insufficient precision of the target numeric and decimal datatype.
For boolean values that map to varchar(5) columns, the adapter inserts the text "true" or "false" into the database table. For boolean values that map to various integer database columns, the adapter inserts values 1 or 0.
Event Stream Processor Datatypes | Adaptive Server Enterprise Datatypes |
---|---|
integer |
tinyint, smallint, unsigned smallint, int, bigint, money, numeric and decimal datatypes with precision - scale >= 10 |
long |
unsigned int, bigint, unsigned bigint, numeric and decimal datatypes with precision - scale >= 19 |
float | double precision, numeric, decimal |
date | date, smalldatetime, datetime, bigdatetime |
timestamp | bigdatetime |
bigdatetime | time, bigtime, bigdatetime, datetime |
string | char(n), varchar(n) |
boolean | bit, tinyint, smallint, int, bigint, unsigned smallint, unsigned int, unsigned bigint, varchar(5) |
money |
smallmoney, money, numeric and decimal datatypes with scale >= 4 |
money(n) |
numeric(p,s) and decimal(p,s)datatypes with scale >= n |
interval | bigint |
binary | binary(n), varbinary(n) |