Re: citext function overloads for text parameters - Mailing list pgsql-hackers

From Shay Rojansky
Subject Re: citext function overloads for text parameters
Date
Msg-id CADT4RqA-6R-tJ48JUcNJRu8QPucR=H5m5-_pWb3q-LC7HRh-hg@mail.gmail.com
Whole thread Raw
In response to citext function overloads for text parameters  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: citext function overloads for text parameters  (Sergey Mirvoda <sergey@mirvoda.com>)
List pgsql-hackers

Thanks for the input. It's worth noting that the equality operator currently works in the same way: citext = text comparison is (surprisingly for me) case-sensitive.

My expectation was that since citext is supposed to be a case-insensitive *type*, all comparison operations involving it should be case-insensitive;

Comparison requires both things to be the same type.  The rules for implicitly converting one type to another prefer the core type text over the extension type citext.

IOW, there is no such operator =(citext,text) and thus "citext = text comparison" is technically invalid.

At this point we're sorta stuck with our choice, and while individual databases can implement their own functions and operators there is value in doing things the way the system provides to minimize future confusion and bugs.

OK, thanks for everyone's input. 

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: citext function overloads for text parameters
Next
From: Sergei Kornilov
Date:
Subject: Re: Having query cache in core