Fw: Arrays

From: Bob Pawley <rjpawley(at)shaw(dot)ca>
To: Postgresql <pgsql-general(at)postgresql(dot)org>
Subject: Fw: Arrays
Date: 2006-01-26 19:27:11
Message-ID: 011c01c622ae$814d52a0$ac1d4318@owner
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


----- Original Message -----
From: "Bob Pawley" <rjpawley(at)shaw(dot)ca>
To: "Karsten Hilbert" <Karsten(dot)Hilbert(at)gmx(dot)net>
Sent: Thursday, January 26, 2006 11:26 AM
Subject: Re: [GENERAL] Arrays

> Because with arrays I can include other information such as pointers to
> conversion factors and hopefully implement systems more easily with all
> pertinent information tied to a single source (single column).
>
> Bob
> ----- Original Message -----
> From: "Karsten Hilbert" <Karsten(dot)Hilbert(at)gmx(dot)net>
> To: <pgsql-general(at)postgresql(dot)org>
> Sent: Thursday, January 26, 2006 11:00 AM
> Subject: Re: [GENERAL] Arrays
>
>
>> On Thu, Jan 26, 2006 at 10:15:22AM -0800, Bob Pawley wrote:
>>
>>> I would like to make a table of 20 plus columns the
>>> majority of columns being arrays.
>>>
>>> The following test works. The array will hold up to five
>>> characteristics of each parameter including the unit of
>>> measurement used. Using traditional methods I would need six
>>> columns to accomplish the same end (Min, Max, Norm plus a
>>> unit column for each).
>> And why would that be undesirable ?
>>
>> Karsten
>> --
>> GPG key ID E4071346 @ wwwkeys.pgp.net
>> E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 6: explain analyze is your friend
>

Browse pgsql-general by date

  From Date Subject
Next Message Matthew T. O'Connor 2006-01-26 19:35:42 Re: VACUUM Question
Previous Message Eric E 2006-01-26 19:25:08 Re: Arrays