1. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jun 2000
    Rep Power
    This question isn't specifically about MySQL, but about database design in general. Suppose, you had a table that was like this:
    <BLOCKQUOTE><font size="1" face="Verdana,Arial,Helvetica">code:</font><HR><pre>
    | part_# | color | cost | description |
    But suppose the description was very lengthy, 10000+ characters. Does it's presence in the table slow down queries against the other fields? Would a query such as SELECT color FROM table WHERE part_#=1 be faster if the descriptions were kept in a separate table?
  2. #2
  3. Banned (not really)
    Devshed Supreme Being (6500+ posts)

    Join Date
    Dec 1999
    Caro, Michigan
    Rep Power
    I think if you do a SELECT *, then it would have adverse effects. As long as you're only selecting the large column when you're actually planning to use it, then it shouldn't matter.

    My $0.02.

    ---John Holmes...
  4. #3
  5. No Profile Picture
    Apprentice Deity
    Devshed Loyal (3000 - 3499 posts)

    Join Date
    Jul 1999
    Niagara Falls (On the wrong side of the gorge)
    Rep Power
    As long as you index the field(s) you will be matching your query on, then no, the large field will not have an adverse affect.

Similar Threads

  1. general web server question
    By black_lotus in forum Apache Development
    Replies: 3
    Last Post: February 7th, 2004, 12:12 AM
  2. database design and paging question
    By emilyb in forum MySQL Help
    Replies: 12
    Last Post: February 5th, 2004, 01:31 PM
  3. a more general question
    By pythone in forum HTML Programming
    Replies: 4
    Last Post: January 20th, 2004, 03:51 AM
  4. Newbie Here - General Code Ethics Question
    By Soniclight in forum Beginner Programming
    Replies: 7
    Last Post: January 16th, 2004, 09:20 PM
  5. Replies: 3
    Last Post: January 7th, 2004, 04:23 PM

IMN logo majestic logo threadwatch logo seochat tools logo