Re: Possible Typecasting Bug with coalesce()

From: "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "MotherMGA" <sbbowers(at)gmail(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Possible Typecasting Bug with coalesce()
Date: 2006-07-19 07:36:10
Message-ID: E1539E0ED7043848906A8FF995BDA579012B442E@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > => select now()>coalesce('Jul 14 2006 9:16:47AM');

> The only bug I see here is that implicit coercions to text
> are a bad idea :-( --- IMHO it would be better if your first
> query failed instead of giving you unexpected behavior.

:-) We know that you think that Tom, but a lot of us do not
want to go casting all our sql, especially where other db's don't
require it.

Would an equivalent CASE statement also do the early conversion to text
?

Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas DCP SD 2006-07-19 07:45:56 Re: [SQL] using constraint based paritioning to fix EAV type schemas? (view inheritance and constraints)
Previous Message Martijn van Oosterhout 2006-07-19 06:45:38 Re: [HACKERS] pg_regress in C