From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
Cc: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Override PostgreSQL internal functions |
Date: | 2014-02-28 08:20:59 |
Message-ID: | CA+U5nM+64OiD_zRmBF9MQCec-EiWh_kBTv==Z2GRh8eK_1VNsw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On 27 February 2014 01:42, Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> wrote:
> On 02/26/2014 03:03 PM, Sameer Kumar wrote:
>
>
> On Wed, Feb 26, 2014 at 6:54 PM, Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> wrote:
>>
>> You would be much better off to use the citext extension and typing your
>> columns appropriately.
>>
>> http://www.postgresql.org/docs/current/static/citext.html
>
>
> That might be a huge effort while migrating from another database and might
> also introduce application level changes for type casting.
>
>
> Not nearly as much effort as what you're trying to do, but good luck.
>
> David's solution is what I would have suggested had he not said it already.
David's solution seems to be the right solution for general schema override.
Vik's comments about using citext seem good for the specific case
mentioned. Using citext has all the same issues as overriding existing
operators, so its better to use something that works than something
home-grown.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | ss dev | 2014-02-28 19:52:11 | XML data |
Previous Message | Simon Riggs | 2014-02-28 08:18:33 | Re: What DBMS_LOCK? |