![INSERT...LOCATION supports 20MB large object (LOB) data [CR 453439]](arrow-left.gif){kind=icon}
![Enabling ODBC trace output [CR 442772]](arrow-right.gif){kind=icon}
Sybase IQ 12.7 ESD #2 supports implicit conversion between BIT and CHAR and BIT and VARCHAR data types for arithmetic, comparison, INSERT, and UPDATE operations.
In Chapter 7, “Moving Data In and Out of Databases,” the tables in the section “Data conversions in IQ” should be updated as follows:
In Table 7-6: “IQ conversions for comparison operations,” the conversion in the rows From: bit To: ch (CHARACTER data type) and From: bit To: vc (VARCHAR data type) should be “I” (implicit) instead of “E” (explicit).
In Table 7-6: “IQ conversions for comparison operations,” the conversion in the rows From: char To: bt (BIT data type) and From: varchar To: bt should be “I” (implicit) instead of “E” (explicit).
In Table 7-7: “IQ conversions for arithmetic operations,” the conversion in the rows From: bit To: ch (CHARACTER data type) and From: bit To: vc (VARCHAR data type) should be “I” (implicit) instead of “E” (explicit).
In Table 7-7: “IQ conversions for arithmetic operations,” the conversion in the rows From: char To: bt (BIT data type) and From: varchar To: bt should be “I” (implicit) instead of “E” (explicit).
In Table 7-8: “IQ conversions for INSERT and UPDATE,” the conversion in the rows From: bit To: ch (CHARACTER data type) and From: bit To: vc (VARCHAR data type) should be “I” (implicit) instead of “E” (explicit).
In Table 7-8: “IQ conversions for INSERT and UPDATE,” the conversion in the rows From: char To: bt (BIT data type) and From: varchar To: bt should be “I” (implicit) instead of “E” (explicit).
