Re: express composite type literal as text

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: express composite type literal as text
Date: 2015-02-22 20:27:13
Message-ID: 20150222202713.GL18747@crankycanuck.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs 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(at)crankycanuck(dot)ca

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2015-02-22 20:56:26 Re: [GENERAL] express composite type literal as text
Previous Message Eric Hanson 2015-02-22 20:18:21 Re: [GENERAL] express composite type literal as text

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2015-02-22 20:56:26 Re: [GENERAL] express composite type literal as text
Previous Message Eric Hanson 2015-02-22 20:18:21 Re: [GENERAL] express composite type literal as text