From: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> |
---|---|
To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Override PostgreSQL internal functions |
Date: | 2014-02-27 05:18:03 |
Message-ID: | CADp-Sm6nMo7eBKaEaBfyNBCNA41426fHp3R5_qkmZWhF8-d=SA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Thu, Feb 27, 2014 at 9:42 AM, Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> wrote:
> Not nearly as much effort as what you're trying to do, but good luck.
Scanning the application code to add casting info could be a pain and I may
not be sure if I have done that for all the function calls/string
comparisons. Moreover I need to repeat this process from scratch for each
customer/migration project.
Whereas if I have something handy (a set of override functions) I can do it
easily for every project. Moreover, PostgreSQL has a very organized list of
functions and decent documentation about arguments and return type. This
makes my task easy for building this one time set of override function. :-)
David's solution is what I would have suggested had he not said it already.
Thanks both of you for your help and suggestions :-)
Best Regards,
*Sameer Kumar | Database Consultant*
*ASHNIK PTE. LTD.*
101 Cecil Street, #11-11 Tong Eng Building, Singapore 069533
M: *+65 8110 0350* T: +65 6438 3504 | www.ashnik.com
*[image: icons]*
[image: Email patch] <http://www.ashnik.com/>
This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s).
From | Date | Subject | |
---|---|---|---|
Next Message | Saret Sout | 2014-02-27 13:13:47 | What DBMS_LOCK? |
Previous Message | Vik Fearing | 2014-02-27 01:42:01 | Re: Override PostgreSQL internal functions |