Re: RfD: more powerful "any" types

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RfD: more powerful "any" types
Date: 2009-09-08 17:11:11
Message-ID: 56D39834-538B-42AF-9E84-62E571DF61EF@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sep 8, 2009, at 9:57 AM, Tom Lane wrote:

> Intentionally so, because there's not a whole lot you can *do* with an
> ANY parameter, other than checking it for null. Perhaps the real
> question is about what semantics you're expecting for these
> unconstrained parameters.

For my purposes, I guess implicit casting for comparing values, as in

arg_a IS DISTINCT FROM arg_b

and

arg_a = arg_b

or

arg_a <> arg_b

It'd work if there was a way to cast one to the type of the other,
such as comparing a TEXT to a VARCHAR. But maybe that'd be too magical…

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-09-08 17:15:59 Re: RfD: more powerful "any" types
Previous Message Tom Lane 2009-09-08 16:57:08 Re: RfD: more powerful "any" types