Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Extended unit
- From: Roman Neuhauser <neuhauser(at)chello(dot)cz>
- To: Pailloncy Jean-Gerard <jg(at)rilk(dot)com>
- Cc: pgsql-general(at)postgresql(dot)org
- Subject: Re: Extended unit
- Date: Tue, 25 Jan 2005 14:15:23 +0100
- Message-id: <20050125131523.GA1269@isis.wad.cz> <text/plain>
# jg(at)rilk(dot)com / 2005-01-25 10:40:15 +0100:
> I add use in my time in University some software that use "extended
> type".
> For each variable, we define the mandatory "classic type" as integer,
> float, double array of.
> And we define an optional "extended type" as the unit in the MKSA
> system (Meter, Kilogram, Second, Ampere) or any other unit we would
> have previously define (eg. Currency).
>
> This "extended type" was wonderful, because there was warning/error if
> "extend type" does not match in any computation: you can not add apple
> to orange.
>
> I would appreciate to have such system in PostgreSQL.
Is CREATE TYPE what you're looking for?
http://www.postgresql.org/docs/8.0/static/sql-createtype.html
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
- Follow-Ups:
- Re: Extended unit
- From: Pailloncy Jean-Gerard
- Re: Extended unit
- References:
- Extended unit
- From: Pailloncy Jean-Gerard
- Extended unit
- Prev by Date: Re: EMBEDDED PostgreSQL
- Next by Date: Re: What is the format of 'binary' data in the postgresql client/server protocol version 3
- Previous by thread: Re: Extended unit
- Next by thread: Re: Extended unit
- Indexes: