From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] varchar() change |
Date: | 1998-01-08 06:16:25 |
Message-ID: | 199801080616.BAA18891@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Come to think of it, I wonder if I could have the disk copy of
> > pg_attribute use the pg_type length, and use the pg_attribute length
> > only when creating/updating entries? I wonder if that is what it does
> > already. Looks like that may be true.
> >
> > Comments?
>
> Is what you are trying to do related to what could be used to implement
> other (SQL92) data types like numeric(precision,scale) where there are one
> or two additional parameters which are assigned when a column/class/type is
> defined and which must be available when working with column/class/type
> instances? We probably don't want to do anything about the latter for v6.3
> (spread pretty thin with the work we've already picked up) but I'd like to
> do something for v6.4...
>
> Oh, while I'm thinking about it, this kind of thing is probably also
> necessary to get arrays working as expected (enforcing dimensions specified
> in the declaration).
Yes, I had the numeric in mind.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-01-08 06:29:55 | varchar() fix |
Previous Message | Vadim B. Mikheev | 1998-01-08 05:54:15 | Re: [HACKERS] rollback varchar change |