Re: Array string casts with SELECT but not SELECT DISTINCT

From: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Array string casts with SELECT but not SELECT DISTINCT
Date: 2015-02-22 04:26:31
Message-ID: CAKFQuwYUMmWwRxC2Wk4R+HVPSxZxCxa7KdotWbksfbHHYk0mzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Feb 21, 2015 at 7:11 PM, Ken Tanzer [via PostgreSQL] <
ml-node+s1045698n5838896h0(at)n5(dot)nabble(dot)com> wrote:

> I tried that and it does indeed work. (With, of course, the appropriate
> permissions to create the cast.)
>
> So this makes me wonder--is there any downside or unwelcome side effects
> to having such a cast? And if not, why isn't it part of the default setup?
>
>
​By and large implicit casts work great if you code everything without
error. When they become a problem is when you make mistakes and because of
implicit casting instead of getting an error you get bogus results.

David J.

--
View this message in context: http://postgresql.nabble.com/Array-string-casts-with-SELECT-but-not-SELECT-DISTINCT-tp5838663p5838901.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Giuseppe Sacco 2015-02-22 07:59:36 Re: Postgres architecture for multiple instances
Previous Message sridhar bamandlapally 2015-02-22 03:36:17 Re: Array string casts with SELECT but not SELECT DISTINCT