From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] cidr |
Date: | 1998-08-11 20:59:28 |
Message-ID: | 199808112059.QAA27850@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Thus spake Bruce Momjian
> > > I do like the idea of using attypmod to define the form of the type.
> > > I assume we can use that to determine the output format, that is, use
> > > it to effectively apply one of the functions to it. That makes for
> > > a clean use of the type.
> >
> > OK. Sounds good to me. The only problem is display. If we don't
> > indicate whether it is a cidr or host/netmask on column creation or
> > insertion, how do we display it so it makes sense? Always cidr?
>
> Well, I guess we just decide on a default format if it is not defined.
> I think the default should be display as cidr (x.x.x.x/y) except omit
> the mask length if it is 32 (or -1 if we go with that usage.) Perhaps
> make one of the defined types always display cidr even in thos special
> cases.
Where are we with this? I think Harouth took this on.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | D'Arcy J.M. Cain | 1998-08-11 21:13:15 | Table permissions problem |
Previous Message | Bruce Momjian | 1998-08-11 20:33:09 | Re: [HACKERS] Indexes bug |