Re: Summary: what to do about INET/CIDR

* Alex Pilosov <alex(at)pilosoft(dot)com> [001027 14:43]:
> On Fri, 27 Oct 2000, Larry Rosenman wrote:
> > ler=# select * from ler_test;
> > net | host
> > ---------------+------------------
> > 207.158.72/24 | 207.158.72.11/24
> > (1 row)
> >
> > ler=# select host(net::inet) from ler_test;
> > ERROR: CIDR type has no host part
> > ERROR: CIDR type has no host part
> I agree. There should be a coercion function, but it should never be
> automatic...But since now there aren't any automatic coercions, that's not
> a problem ;)
>
> Also, I agree with Larry that cidr _must_ be printed with 4 octets in
> them, whether they are 0 or not. (i.e. it should print 207.158.72.0/24)
>
> This is the standard way of specifying addresses in all network equipment.
> RFC specifies that, just the library that we use doesn't (yes, it is from
> Vixie, but it doesn't make it RFC-compliant)
and network(cidr) should print ONLY the octets, not the mask...

LER

>
> I'll submit patches in a week or so, when I start straightening out my
> network equipment tables...;)
>
> -alex

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749