| From: | "Steve Clark" <sclark(at)netwolves(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #4007: chr(0) doesn't work anymore |
| Date: | 2008-03-03 15:28:04 |
| Message-ID: | 200803031528.m23FS4G9040185@wwwmaster.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
The following bug has been logged online:
Bug reference: 4007
Logged by: Steve Clark
Email address: sclark(at)netwolves(dot)com
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 coalesce(param_value,chr(0)) from t_system_params where param_name =
'default_unit_key';
it now fails with:
ERROR: null character not permitted
The documentation says:
For other multibyte encodings the argument must designate a strictly ASCII
character.
NUL = 0 is a valid ascii character.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-03 15:49:39 | Re: BUG #4007: chr(0) doesn't work anymore |
| Previous Message | Steve Clark | 2008-03-03 15:17:04 | Re: ecpg produces code that won't compile |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-03 15:49:39 | Re: BUG #4007: chr(0) doesn't work anymore |
| Previous Message | kenneth d'souza | 2008-03-03 04:19:30 | Reference by output in : \d <table_name> |