Re: citext operator precedence fix

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: citext operator precedence fix
Date: 2011-09-22 17:06:00
Message-ID: 5F69FDD9-6A20-4280-8BB4-32B99C6212E7@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sep 22, 2011, at 9:53 AM, Josh Berkus wrote:

>>
>> Then the question is: does it find only #2 via polymorphic lookup, or does it think that either #1 or #2 could work (because text supports an implicit cast to citext, IIRC). If it's more than one it's an error. Not sure if the same issue exists for operators.
>
> Well, I just ran through the 7 potential combinations, and didn't get
> any errors. Hard to tell which function is being used, of course.

That's what tests are for.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2011-09-22 17:11:25 Re: citext operator precedence fix
Previous Message Josh Berkus 2011-09-22 16:53:55 Re: citext operator precedence fix