| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Łukasz Odziewa <disk(at)ceti(dot)pl> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: maybe a bug? |
| Date: | 2001-09-27 14:49:37 |
| Message-ID: | 17132.1001602177@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?iso-8859-2?Q?=A3ukasz_Odziewa?= <disk(at)ceti(dot)pl> writes:
> I have problem with new PGSQL 7.1.3
> I've a table like that TT ( V VARCHAR(10), D DATE, I INTEGER);
> and query "SELECT V || '</TD><TD>' || D || '</TD><TD>' || I FROM TT;"
> In version 7.1.2 result is '$V</TD><TD>$D</TD><TD>$I' when $? means text
> representation of ?. It's always true even if any $? is NULL.
> In version 7.1.3 result is '$V</TD><TD>$D</TD><TD>$I' or NULL if any of
> $? is NULL.
The behavior you attribute to 7.1.3 is correct, and would have been the
same in any 7.1.* release. I do not believe that 7.1.2 would have been
different.
Try COALESCE(foo::text, '') if you want to substitute an empty string
for NULL values.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2001-09-27 16:11:47 | Re: time's running short for you to reserve 5432/tcp!!!! |
| Previous Message | Tom Lane | 2001-09-27 14:35:18 | Re: Bug #470: INTERSECT fails |