On Fri, 30 May 2003, Josh Berkus wrote:
> Jeandre,
>
> > instead of normalizing the database. I think that they think that joining
> > tables will slow down retrieval, is this true?
>
> No, it's not. I'm afraid that your co-workers learned their computer
> knowledge 10 years ago and have not kept up to date. They may need
> retraining.
Thought as much
>
> Modern database systems, especially PostgreSQL, are much faster with a proper
> relational schema than with an inadequate flat-file table, due to the
> efficient storage of data ... i.e., no redundancy.
That is what I thought, but since they out rank me at work I needed the
extra conformation. Now at least I can show them that I am not the only
person that thinks a flat table structure is stone age design. I know for a
fact it is better on Sybase, but I wasn't to sure about postgres and since
they have been working on it for longer than I have, I am expected to
follow their lead.
>
> I highly suggest that you take a look at the book "Database Design for Mere
> Mortals"; if you're asking the question you posted, you are nowhere near
> ready to build a production database application.
>
Thanks, I will have a look at that book. You are right, I am only first
year Bsc, but I had a feeling that the facts they are giving me can't be
right, it just didn't make any sense. They way I figured it, is that
having a relational database, makes the database smaller because there is
no duplicate data, which should make it faster.
Thanks for your help. I will approach my managers.
Jeandre