Re: Differences in WHERE clause of SELECT

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Differences in WHERE clause of SELECT
Date: 2013-07-16 18:58:05
Message-ID: CAHyXU0z6sPrRDFwtRB6iT+L3TROLfbPOS680KAvjJOH0iD9PCQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 16, 2013 at 12:58 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> PostgreSQL requires more casts that any other mainstream database
> system on the planet, and it's one of the biggest barriers to
> migrating from other database systems to PostgreSQL. I understand
> that there is a consensus in this forum to pretend that our
> intolerance is a virtue, but I don't agree with that consensus. A
> request for =(text,int) is ambiguous; we really do not know what is
> meant. A request for ~~(int,text) is not ambiguous; we reject it out
> of pedantry, not necessity.

You make some good points but I still wonder (I'm recalling your lpad
discussion from a while back) if we're better off providing specific
overloads and casts for portability pain points instead of changing
casting mechanics.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Wanner 2013-07-16 19:14:17 Re: Proposal: template-ify (binary) extensions
Previous Message Kevin Grittner 2013-07-16 18:38:31 Re: refresh materialized view concurrently