From: Aaron Bono <postgresql@aranya.com>
To: pgsql-sql@postgresql.org
Subject: Re: COPY to table with array columns (Longish)
Date: Mon, 12 Jun 2006 23:11:43 -0500
Message-ID: <bf05e51c0606122111m78e56216p3f0515cb5885fe1f@mail.gmail.com> (raw)
In-Reply-To: <008801c68e98$0cb1a620$9b0014ac@ITPhil>
References: <bf05e51c0606121958i54a7833bt76bb8756dd41aec1@mail.gmail.com>
<008801c68e98$0cb1a620$9b0014ac@ITPhil>
I think two tables should suffice: ZKCOST and ZPRECMPL.
So you would have
ZKCOST
zkcost_id,
zkcost_value
and
ZPRECMPL
zkcost_id,
zprecmpl_id,
zprecmpl_value
where zkcost_id is the primary key for ZKCOST and zkcost_id,
zprecmpl_id together are the primary key for ZPRECMPL and zkcost_id is
a foreign key from ZPRECMPL to ZKCOST.
That will work won't it?
-Aaron
On 6/12/06, Phillip Smith <phillips@weatherbeeta.com.au> wrote:
> So you're suggesting creating a child table for each SYS record? Ie, a table called "ZPRECMPL" etc?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: postgresql@aranya.com
Subject: Re: COPY to table with array columns (Longish)
In-Reply-To: <bf05e51c0606122111m78e56216p3f0515cb5885fe1f@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox