Re: Extended unit - Mailing list pgsql-general

From Tom Lane
Subject Re: Extended unit
Date
Msg-id 8002.1106693926@sss.pgh.pa.us
Whole thread Raw
In response to Re: Extended unit  (Pailloncy Jean-Gerard <jg@rilk.com>)
Responses Re: Extended unit  (Richard Huxton <dev@archonet.com>)
List pgsql-general
Pailloncy Jean-Gerard <jg@rilk.com> writes:
> I do not want for each column and each row to store the value and the
> unit.

> I do want to put the unit in the definition of the column and the check
> on the parser before any execution.

If you do that, you foreclose the ability to store mixed values in a
single column, in return for what?  Saving a couple of bytes per value?
(I suppose that in a serious implementation we'd store the units as some
sort of reference, not as a string.)  Compare the implementation of the
NUMERIC type: you *can* constrain a column to have a fixed precision,
but you do not *have* to.

            regards, tom lane

pgsql-general by date:

Previous
From: David Siebert
Date:
Subject: Problem with Postgres V 8 and DBI maybe
Next
From: David Garamond
Date:
Subject: Re: EMBEDDED PostgreSQL