Results 1 to 4 of 4
  1. #1
    Join Date
    Feb 2004
    Posts
    13

    1 to 1 is a fault design?

    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

  2. #2
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002
    no
    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

  3. #3
    Join Date
    Jun 2003
    Location
    USA
    Posts
    1,032
    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...
    J. Paul Schmidt, Freelance Web and Database Developer
    www.Bullschmidt.com
    Access Database Sample, Web Database Sample, ASP Design Tips

  4. #4
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002
    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
    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •