| From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bug in create operator and/or initdb |
| Date: | 2005-01-30 02:46:34 |
| Message-ID: | 5066E5A966339E42AA04BA10BA706AE56241@rodrick.geeknet.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
> My opinion is that this is a very bogus shortcut in the
> network datatype code. There are no cases outside the
> inet/cidr group where an operator doesn't exactly match its
> underlying function. (The whole business of inet and cidr
> being almost but not quite the same type is maldesigned
> anyway...)
>
> The right solution for you is to declare two SQL functions.
> Whether you make them point at the same underlying C code is
> up to you.
Right,...
In that case may I suggest fixing the catalog so network_* functions exists for both datatypes!
Anything less I'd consider inconsistent...
Kind regards,
John
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-01-30 03:07:30 | Re: Bug in create operator and/or initdb |
| Previous Message | Tom Lane | 2005-01-30 02:42:49 | Re: Bug in create operator and/or initdb |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-01-30 02:47:59 | Re: Continue transactions after errors in psql |
| Previous Message | Tom Lane | 2005-01-30 02:42:49 | Re: Bug in create operator and/or initdb |