I use npgsql 1.0 to access a PostgreSql 8.2.3 database. Recently, I decided to test with standard_conforming_strings = on and I noticed that npgsql still sends double-backslashes, which corrupts the data.

This is especially bad with byte arrays: if I insert N bytes I get back 4*N bytes because \123 (one byte) becomes \\123 (4 bytes).

Is this a bug in npgsql, or is there some way I can get npgsql to realize that postgres is using standard_conforming_strings?

Thanks,
Bill

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to