From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | gav <gav(at)nlr(dot)ru>, Mitch Vincent <mitch(at)venux(dot)net>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Re[2]: lower() for varchar data by creating an index |
Date: | 2000-05-18 15:28:37 |
Message-ID: | 200005181528.LAA19588@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> Alex Guryanow <gav(at)nlr(dot)ru> writes:
> > my-db=> DROP FUNCTION lower(varchar);
> > ERROR: RemoveFunction: function "lower" is built-in
>
> You can get rid of it by deleting the pg_proc tuple directly. I wonder
> though whether RemoveFunction isn't being overly protective --- is there
> any good reason not to allow people to delete built-in functions?
> Obviously you have only yourself to blame if you delete integer equals
> or something equally critical ;-) ... but there are a boatload of
> built-ins that are by no means critical. Comments anyone?
I would throw a notice and keep going. Should I commit the change?
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-18 15:41:52 | Re: Re[2]: lower() for varchar data by creating an index |
Previous Message | Bruce Momjian | 2000-05-18 15:20:05 | Re: Using substr with user defined types |