> Okay, then what we have in the repository now should work. Alright, this time I have tested it more properly with all possible byte values. The current version breaks for at least backslashes.
I would suggest completely eliminating the special casing of certain characters - that is, never even using escapechar(). Since the data being worked on is never likely to be read by humans - except when debugging things like this - readability does not seem that important compared to eliminating special cases for ranges. I have tested a version of the table writer that does octal escaping for all unprintable charcters, and it works for all possible byte values and for both the BYTEA type and VARCHAR volumn type (all 2x256 permutations tested). -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org
pgpWpOFSklQ7E.pgp
Description: PGP signature
_______________________________________________ Libpqxx-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
