Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: Mike Sosteric <mikes@athabascau.ca>
Subject: Re: [GENERAL] arrays
Date: Mon, 30 Sep 2002 11:20:09 -0700
Cc: pgsql-sql@postgresql.org
References: 
 <Pine.SUN.3.96.1020930120856.18945B-100000@aupair.cs.athabascau.ca>
In-Reply-To: 
 <Pine.SUN.3.96.1020930120856.18945B-100000@aupair.cs.athabascau.ca>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200209301120.09427.josh@agliodbs.com>


Mike,

> 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.=20

This looks soluable several ways.=20=20=20

Question #1:  If each record has 67 fields, and each field may appear in=20
several languages, is it possible for some fields to be in more languages=
=20
than others?  I.e. if "title-en" and "title-de" exist, does it follow that=
=20
"content-en" and "content-de" exist as well?   Or not?

Question #2: Does your XML schema allow locall defined attributes?  That is=
,=20
do some records have entire attributes ("fields" ) that other records do no=
t?

Suggestion #1:  Joe Celko's "SQL for Smarties, 2nd Ed." is an excellent boo=
k=20
for giving you ideas on how to adapt SQL structures to odd purposes.

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco