Re: Summary: what to do about INET/CIDR

Поиск
Список
Период
Сортировка
От Alex Pilosov
Тема Re: Summary: what to do about INET/CIDR
Дата
Msg-id Pine.BSO.4.10.10010271537130.7430-100000@spider.pilosoft.com
обсуждение исходный текст
Ответ на Re: Summary: what to do about INET/CIDR  (Larry Rosenman <ler@lerctr.org>)
Ответы Re: Summary: what to do about INET/CIDR
Re: Summary: what to do about INET/CIDR
Re: Summary: what to do about INET/CIDR
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Lamar Owen
Дата:
Сообщение: Re: Re: [GENERAL] 7.0 vs. 7.1 (was: latest version?)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Idea: cross-check versions during initdb