Re: express composite type literal as text - Mailing list pgsql-general

From Andrew Sullivan
Subject Re: express composite type literal as text
Date
Msg-id 20150222202713.GL18747@crankycanuck.ca
Whole thread Raw
In response to Re: express composite type literal as text  (Eric Hanson <elhanson@gmail.com>)
List pgsql-general
On Sun, Feb 22, 2015 at 12:18:21PM -0800, Eric Hanson wrote:
> Got it.  Ok, I'm reporting this as a bug.  Is this a bug?  Being able to
> always express literals as text is a really valuable assumption to be able
> to rely on.

If I had to guess (I guess someone more authoritative than I will
chime in), I suspect this is a side effect of the change a few years
ago that removed a very large number of automatic typecasts.
Experience with those automatic typecasts revealed that while they
were handy lots of the time, when they failed they did really bad
things.  So the developers dramatically reduced the number of such
cases.  Some convenience was lost (I still get tripped up from time to
time, but I'm not doing Pg work every day), but the overall
reliability of things was increased.  So I'd say it's probably not a
bug.

A

--
Andrew Sullivan
ajs@crankycanuck.ca


pgsql-general by date:

Previous
From: Eric Hanson
Date:
Subject: Re: express composite type literal as text
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] express composite type literal as text