Occasionally, we get bitten by embedded NUL bytes in TEXT values. We
take care of generating proper UTF-8, but this additional restriction
sometimes slips by. It would be really helpful if PostgreSQL could
store such TEXT fields as-is (at least if they are computed internally,
or come from query parameters).
I haven't even looked how difficult it would be to implement this. Do
you think it's worth the trouble?
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
pgsql-hackers by date
|Next:||From: Pavel Stehule||Date: 2011-11-24 09:21:21|
|Subject: Re: Making TEXT NUL-transparent|
|Previous:||From: Florian Weimer||Date: 2011-11-24 09:03:25|
|Subject: Wire protocol: type-specific opt-in to binary format|