Hi,

> > What "fastest" - table design shouldn't be about speed, but about
> > consistency and normalized data structures.
>
> The reality is never as black and white as you've suggested.

Of course you are right - but starting with "what is the fastest table
design" isn't the right way. First, design "right" - then tweak.

> Admittedly, a database design should meet the criteria you outlined.
>
> However, there are allowance/situations where *some* denormalization is
> appropriate and beneficial.

On the other hand, denormalization adds the overhead of updating in multiple
tables, integrity errors/checking/updating etc etc...

So still, instead of "working around" the problem, people should "tell" or
push the db vendors into creating a better and more efficient engine.

They will only improve if they get feedback from developers.


With regards,

Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."