Re: Postgresql and programming

If you're only consideration is raw performance of lookups on text
fields, I suppose there might be some measureable performance advantage
in putting everything in one table, but I doubt you'd really notice the
difference. If you *did* do this, what is the significance of the
authorID field?

Normalize, normalize, normalize. Use a relational database for it's
strengths. Don't duplicate data.

"T.J.Farrell" wrote:
>
> In terms of performance also, is it preferable to desing a database as:
>
> create table articles (
> refarticle text,
> title text,
> authorID integer,
> authorname text,
> editorID integer,
> editorname text,
> ... etc...
> );
>
> OR :
>
> create articles(
> refarticle text,
> title text,
> authorID integer,
> editorID integer,
> ... etc...
> );
>
> create table authors(
> authorname text,
> authorID integer,
> ...etc...
> );
>
> create table editors(
> editorID integer,
> editorname text,
> ...etc...
> );

________________________
Ron Peterson
rpeterson(at)yellowbank(dot)com