Re: Possible Typecasting Bug with coalesce() - Mailing list pgsql-hackers

From Zeugswetter Andreas DCP SD
Subject Re: Possible Typecasting Bug with coalesce()
Date
Msg-id E1539E0ED7043848906A8FF995BDA579012B442E@m0143.s-mxs.net
Whole thread Raw
In response to Re: Possible Typecasting Bug with coalesce()  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: [PATCHES] pg_regress in C
Next
From: "Zeugswetter Andreas DCP SD"
Date:
Subject: Re: [SQL] using constraint based paritioning to fix EAV type schemas? (view inheritance and constraints)