MySQL Multiple Columns vs Single Column for speed/optimization

Question

I'm working on a database that describes different physical characteristics of certain people.

My question is, would performance be quicker/less of a workload to have multiple columns setup like so:

HAIR | EYES | HEIGHT | WEIGHT
brwn | blue | 5'9"   | 150

Or have a single column separating the data with delimiter, like so:

ATTRIBUTES
Hair: Brown,
Eyes: Blue,
Height: 5'9",
Weight: 150

Does one have an edge of the other?

JoelFan · Accepted Answer · 2012-04-18 00:10:51Z

2

You should have separate columns for each attribute. Otherwise why are you even using a database?

answered Apr 18, 2012 at 0:10

JoelFan

38.9k38 gold badges143 silver badges218 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

OMG Ponies Over a year ago

+1: Trying to get specifics, like the number of people with blue eyes would be incredibly painful

Rob · Accepted Answer · 2012-04-18 00:11:33Z

1

The performance difference would be minimal, if any. The problem with delimiting the data in a single column is that it makes it more difficult and resource intensive to perform a search. What if you want to find all people that weight between 150 and 160 and have blonde hair? Wont be that easy with it all stuffed in a single column.

answered Apr 18, 2012 at 0:11

Rob

12.9k4 gold badges44 silver badges57 bronze badges

1 Comment

OMG Ponies Over a year ago

Impact depends on the operation

Collectives™ on Stack Overflow

MySQL Multiple Columns vs Single Column for speed/optimization

2 Answers 2

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related