Steve Clark <[EMAIL PROTECTED]> writes:
> I'm not sure I understand what you mean about TEXT being null-safe.
> What are the issues, and why was
> it supported for years and now abruptly changed.
It never was supported, we are simply plugging a hole that let you
create a text value that would be
Tom Lane wrote:
"Steve Clark" <[EMAIL PROTECTED]> writes:
Until 8.3.0 the following worked:
SELECT coalesce(param_value,chr(0)) from t_system_params where param_name =
'default_unit_key';
It would have "worked" only for rather small values of "work", since
most of the support for type TEXT
"Steve Clark" <[EMAIL PROTECTED]> writes:
> Until 8.3.0 the following worked:
> SELECT coalesce(param_value,chr(0)) from t_system_params where param_name =
> 'default_unit_key';
It would have "worked" only for rather small values of "work", since
most of the support for type TEXT isn't null-safe.
The following bug has been logged online:
Bug reference: 4007
Logged by: Steve Clark
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: FreeBSD 6.2
Description:chr(0) doesn't work anymore
Details:
Until 8.3.0 the following worked:
SELECT co
