I wrote:
> "David E. Wheeler" <[EMAIL PROTECTED]> writes:
>> Anyway, would this issue then go away once the type stuff was added
>> and citext was specified as TYPE = 'S'?
> Yeah, that's the point of the proposal.
BTW, I did confirm (by temporarily hacking up TypeCategory()) that
causing citext to appear to be of STRING category eliminates the need
for the extra || operator and quote_literal() function that are in
the current citext code. So the proposed solution really will work.
You might still want to keep the aliases in cases where the point is to
have the function or operator output resolve as citext rather than text.
I'm not sure how many of these cases that's really important for,
though.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
