From: | "Larry Rosenman" <ler(at)lerctr(dot)org> |
---|---|
To: | <pgsql-hackers(at)hub(dot)org>, "Larry Rosenman" <ler(at)lerctr(dot)org> |
Cc: | "Don Baccus" <dhogaza(at)pacifier(dot)com> |
Subject: | RE: INET/CIDR types |
Date: | 2000-07-24 21:11:34 |
Message-ID: | NCBBKBDOOHHEJCJHLLPAIELMHIAA.ler@lerctr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Can we dig up the RFC?
Larry
-----Original Message-----
From: pgsql-hackers-owner(at)hub(dot)org [mailto:pgsql-hackers-owner(at)hub(dot)org]On
Behalf Of D'Arcy J.M. Cain
Sent: Monday, July 24, 2000 3:53 PM
To: Larry Rosenman
Cc: pgsql-hackers(at)hub(dot)org; Don Baccus
Subject: Re: [HACKERS] INET/CIDR types
Thus spake Larry Rosenman
> What RFC says you can't print all 4 octets of a CIDR Netnumber?
Can't recall. It was Paul Vixie who made the claim and since he was
probably the one who wrote it I tend to believe him.
In fact it may be that it suggested rather than required but someone
would have to dig out the RFC before we considered changing it I think.
> Why does network(cidr) return the whole cidr output just like
> select cidr?
Yah, it's redundant. "network(cidr)" is just a long way to say "cidr."
The only reason it is there is because of the way the code was written
for the two types. Not having it would have required a special test to
look for it and technically it is correct so we didn't bother.
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
From | Date | Subject | |
---|---|---|---|
Next Message | Sevo Stille | 2000-07-24 22:29:42 | Re: INET/CIDR types |
Previous Message | D'Arcy J.M. Cain | 2000-07-24 20:53:24 | Re: INET/CIDR types |