> Hmm, so essentially we'd have to convert all codes >= 0x80 to prevent > them from being mistaken for parts of multibyte sequences?
Yes. > Ugh, but > you're probably right. It looks to me like byteaout does the reverse > already. As for the new UNKNOWN data type, that seems a good thing for me. However, I think more aggressive soultion would be having an encoding info in the text data type itself. This would also opens the way to implement SQL99's CREATE CHARACTER SET stuffs. I have been thinking about this for a while and want to make a RFC in the future(I need to rethink my idea to adopt the SCHEMA you introduced). BTW, for the 7.2.x tree we need a solution with lesser impact. For this purpose, I would like to change PQescapeBytea as I stated in the previous mail. Objection? -- Tatsuo Ishii ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
