| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | PostgreSQL general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Function to Pivot data |
| Date: | 2002-02-11 13:39:38 |
| Message-ID: | 20020211133938.GA3472@wolff.to |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > This is the real problem: for any given book, you can't know in
> > advance how many authors it might have. It's why I sort of thought
> > that a simple lookup table approach wouldn't be a good answer for
> > this: you have an ordered data set of unpredictable size for every
The way I did this for a tiny book database I have set up for my wife
to keep track of books is to have an edition table, an author table and
a table of edition author pairs. It isn't ordered, but it could be
by adding another field to the edition, author pairs.
I haven't finished all of the web based tools for dealing with this,
as she isn't doing a lot with it now, but if you want to look at the
scheme and the web tools that are there, you can look at:
http://wolff.to/book/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2002-02-11 13:46:11 | Re: getting currval from a sequence |
| Previous Message | Cornelia Boenigk | 2002-02-11 13:35:21 | timespan_part()? |