| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: inet/cidr wierdness (casting) |
| Date: | 2001-06-12 15:19:36 |
| Message-ID: | 8770.992359176@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alex Pilosov <alex(at)pilosoft(dot)com> writes:
> Apparently, since there's no explicit function to cast from inet to cidr,
> postgresql assumes its always safe to do so, as they are
> binary-compatible.
Yes. I've thought for awhile that it was a mistake to treat them as
binary-compatible. However, you'd need a lot more operator/function
declarations if they're not so marked.
> Anyone mind if I create explicit function for this so
> this could be flagged as error?
Won't help if they are binary compatible...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-06-12 15:21:16 | Re: Australian timezone configure option |
| Previous Message | Bruce Momjian | 2001-06-12 15:18:29 | Re: Australian timezone configure option |