Re: [GENERAL] arrays

From: Mike Sosteric <mikes(at)athabascau(dot)ca>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: [GENERAL] arrays
Date: 2002-09-30 18:11:36
Message-ID: Pine.SUN.3.96.1020930120856.18945B-100000@aupair.cs.athabascau.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-sql

On Mon, 30 Sep 2002, Josh Berkus wrote:

Don't worry.

Our biggest problem is that each XML data entry, say

<title=en>This is the title</title>

has an language attribute. if there are, say 67 seperate items, each with
multiple languages, then the comlexity of the table structure skyrockets
because you have to allow for multiple titles, multiple names, multiple
everything.

the resulting relational model is icky to say the least. The question, is
how to simplify that. I had thought arrays would help because you can
store the multiple language strings in a single table along with other
records..

any ideas?

m

>
> Mike,
>
> > thanks for this. we will stick with the relational model.
>
> Hey, don't make your decision entirely based on my advice. Do some
> research! I'm just responding "off the cuff" to your questions.
>
> If you do take the relational approach, post some sample problems here and
> people can help you with how to represent XML data relationally.
>
> --
> -Josh Berkus
> Aglio Database Solutions
> San Francisco
>
>

Mike Sosteric <mikes(at)athabascau(dot)ca> Managing Editor, EJS <http://www.sociology.org/>
Department of Global and Social Analysis Executive Director, ICAAP <http://www.icaap.org/>
Athabasca University Cell: 1 780 909 1418
Simon Fraser University Adjunct Professor
Masters of Publishing Program
--
This troubled planet is a place of the most violent contrasts.
Those that receive the rewards are totally separated from those who
shoulder the burdens. It is not a wise leadership - Spock, "The Cloud Minders."

___
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-09-30 18:14:44 Re: pg_* description
Previous Message Tom Lane 2002-09-30 17:59:00 Re: [SQL] CURRENT_TIMESTAMP

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-09-30 18:11:42 Re: 7.2.3?
Previous Message Tom Lane 2002-09-30 18:00:46 Re: Do we want a CVS branch now?

Browse pgsql-sql by date

  From Date Subject
Next Message Josh Berkus 2002-09-30 18:20:09 Re: [GENERAL] arrays
Previous Message Tom Lane 2002-09-30 17:59:00 Re: [SQL] CURRENT_TIMESTAMP