Dear All,
I saw from some other web sites which say that if a database has 1 to 1 relationship, it means that it's a "sign" of bad design, might need to improve... but ... is that true???

thx,

neil

no

I've also often heard that if you have a 1-to-1 relationship, why not just keep things simple by sticking it all in one table...

why not stick it in one table?

here's an example

table1
id integer
foo varchar(5)

table2
id integer
bar longtext -- or similar "large" datatype


suppose you combined these but most of your queries just needed foo, not bar

the combined rows are larger, therefore fewer of them on a physical block on disk, therefore more disk reads to scan the table, therefore slower query

or something like that