From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | "Mr(dot) Tomcat" <tomcat(at)mobile(dot)mp> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Design question: Using Array datatypes |
Date: | 2002-09-24 06:42:47 |
Message-ID: | Pine.GSO.4.44.0209240940460.16105-100000@ra.sai.msu.su |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 23 Sep 2002, Mr. Tomcat wrote:
> I noticed that PG supports arrays. I noticed also that one of the rules
> of DB normalization is "no repeating fields". It seems like using
> arrays would violate that. I have a particular need that would benefit
> from using arrays. There will be no need to search elements in the
> array, so it seems like a good place to use it. What are opinions on
> array usage? Is it a horrible misfeature, never to be used, or is it
> the right way to go in some situations? I have never used arrays in a
> db design.
>
> Thanks for an opinions on this.
contrib/intarray is what you need. We use arrays extensively and rather
happy. It's not a "repeating fields", it's a field with "repeating elements"
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2002-09-24 07:02:43 | Re: Postgresql Automatic vacuum |
Previous Message | Mario Weilguni | 2002-09-24 06:42:06 | Re: Postgresql Automatic vacuum |