Re: Summary: what to do about INET/CIDR - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Summary: what to do about INET/CIDR
Date
Msg-id Pine.LNX.4.21.0011051406290.780-100000@peter.localdomain
Whole thread Raw
In response to Re: Summary: what to do about INET/CIDR  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Summary: what to do about INET/CIDR
Re: Summary: what to do about INET/CIDR
List pgsql-hackers
Tom Lane writes:

> Peter Eisentraut <peter_e@gmx.net> writes:
> > A separate function for formatting output seems necessary, but if we don't
> > reach an agreement though, it ought to work to cast CIDR to INET to get
> > all four octets, no?
> 
> Uh, weren't you one of the people objecting to relying on cidr-to-inet
> casts to control formatting?

I didn't like the use of the to-text casts to control formatting, but if
an existing cast would "just handle it", then why not?

> > I think the typecast-to-text representation of CIDR should be visually the
> > same as the normal representation.
> 
> Well, we need *some* way to extract a representation like "w.x.y.z/n".
> If you don't like text() as the name of that formatting function,
> suggest another name...

all_octets(cidr)::text maybe?

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: "Vadim Mikheev"
Date:
Subject: Re: Transaction ID wraparound: problem and proposed solution
Next
From: Larry Rosenman
Date:
Subject: Re: Summary: what to do about INET/CIDR