Skip site navigation (1) Skip section navigation (2)

Re: Summary: what to do about INET/CIDR

From: Alex Pilosov <alex(at)pilosoft(dot)com>
To: Larry Rosenman <ler(at)lerctr(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Summary: what to do about INET/CIDR
Date: 2000-10-27 19:43:42
Message-ID: Pine.BSO.4.10.10010271537130.7430-100000@spider.pilosoft.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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)

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

-alex


In response to

Responses

pgsql-hackers by date

Next:From: Larry RosenmanDate: 2000-10-27 19:45:58
Subject: Re: Summary: what to do about INET/CIDR
Previous:From: Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=Date: 2000-10-27 19:42:15
Subject: Re: Re: [GENERAL] 7.0 vs. 7.1 (was: latest version?)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group