| From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | inet/cidr wierdness (casting) |
| Date: | 2001-06-12 13:58:21 |
| Message-ID: | Pine.BSO.4.10.10106120955380.17529-100000@spider.pilosoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
In case Tom isn't sick of me yet...
users=# select '10.1.2.3/24'::inet::cidr;
?column?
-------------
10.1.2.3/24
while:
users=# select '10.1.2.3/24'::cidr;
ERROR: invalid CIDR value '10.1.2.3/24': has bits set to right of mask
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. Anyone mind if I create explicit function for this so
this could be flagged as error?
-alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-06-12 14:01:02 | Re: AW: Re: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. Stand ards |
| Previous Message | Zeugswetter Andreas SB | 2001-06-12 13:50:09 | AW: AW: Postgres Replication |