RE: INET/CIDR types - Mailing list pgsql-hackers

From Larry Rosenman
Subject RE: INET/CIDR types
Date
Msg-id NCBBKBDOOHHEJCJHLLPACELCHIAA.ler@lerctr.org
Whole thread Raw
In response to RE: INET/CIDR types  (Don Baccus <dhogaza@pacifier.com>)
Responses Re: INET/CIDR types  (darcy@druid.net (D'Arcy J.M. Cain))
List pgsql-hackers
I was hoping to have some niceties out of the SQL retrieve to print directly
in PHP, and not have to massage it. 

Why is there such animosity to printing out all 4 octets in some function
somewhere for a CIDR block?

Larry 

-----Original Message-----
From: Don Baccus [mailto:dhogaza@pacifier.com]
Sent: Monday, July 24, 2000 2:30 PM
To: Larry Rosenman; pgsql-hackers@hub.org; Larry Rosenman
Subject: RE: [HACKERS] INET/CIDR types


At 02:26 PM 7/24/00 -0500, Larry Rosenman wrote:
>The problem is NON-TECHNICAL people will be getting the output,
>and they expect 4 octet output. 
>
>I really think that we should have a way to coerce a CIDR to
>an INET, and then allow host(). 
>
>Remember that I am dealing with $10/hour clerks. 
>
>I really don't get the hostility to changing the OUTPUT format...

Are these $10/hour clerks typing in SQL to psql?  Strange ...

If not, formatting issues like this can easily be broken (or fixed,
according to your POV) by your application client.



- Don Baccus, Portland OR <dhogaza@pacifier.com> Nature photos, on-line guides, Pacific Northwest Rare Bird Alert
Serviceand other goodies at http://donb.photo.net.
 


pgsql-hackers by date:

Previous
From: Don Baccus
Date:
Subject: RE: INET/CIDR types
Next
From: darcy@druid.net (D'Arcy J.M. Cain)
Date:
Subject: Re: INET/CIDR types