Conversions

Each incoming Rendezvous message must contain nothing but flat data fields (in other words, no submessages or repeated fields), each named precisely the same as a column in the Sybase CEP schema for the associated input stream (text case is significant). If there is not a TIBCO data field with the same name as a given Sybase CEP schema column, the Sybase CEP row produced will have a NULL value for that column. Thus, an empty Rendezvous message would yield a row with all columns NULL.

Rendezvous fields are converted to Sybase CEP values based on the data type of the Sybase CEP column. The acceptable conversions are shown below:

Tibco Rendezvous Data Type	Sybase CEP Data Type
String IPPort16 IPAddr32	String
Boolean	Boolean
Boolean (0= false, 1= true) Signed/unsigned 8-bit integer Signed/unsigned 16-bit integer Signed/unsigned 32-bit integer Signed/unsigned 64-bit integer (overflow results in NULL) IPPort16 IPAddr32	Integer (32-bit)
Boolean (0= false, 1= true) Signed/unsigned 8-bit integer Signed/unsigned 16-bit integer Signed/unsigned 32-bit integer Signed/unsigned 64-bit integer IPAddr32	Long (64-bit)
Signed/unsigned 8-bit integer Signed/unsigned 16-bit integer Signed/unsigned 32-bit integer Signed/unsigned 64-bit integer	Interval (64-bit)
DateTime	Timestamp (64-bit)
32-bit Float 64-bit Float	Float (64-bit)
XML	XML
Opaque IPPort16 IPAddr32 ENCRYPTED	BLOB
I8Array U8Array I16Array U16Array I32Array U32Array I64Array U64Array F32Array F64Array StringArray	Unsupported

For any Sybase CEP schema column of type Interval, the corresponding Rendezvous field should be of type Signed 64-bit Integer (or a smaller signed/unsigned Rendezvous integer data type), which will contain a value representing the number of microseconds in the interval.

It is the responsibility of the user to properly interpret the BLOB data that results from converting TIBCO datatypes to BLOB. Users will probably write User-Defined Functions (UDFs) to interpret this input.