|Problems? Is your data what you think it is?|
There have been a number of replies now that give a more "ideal" solution. But let's take the OP at face value (as reinforced by a later comment) and accept that he has restrictions that preclude the "better" solutions.
Doing that yields the simpler (but not "ideal" from a DB perspective) of this:
One should probably trim any possible leading and/or trailing whitespace just to be safe. Is this an ideal solution? No. Can it be converted to a better solution later if desired? Yes, and without much hassle.
So rather than point all the problems that the OP has with this (at great length in some cases) just take the OP at his word that he understands all of this and appears to have restrictions that dictate that the less than ideal solution be used.
It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.
In reply to Re: Storing multiple value field in a MySQL database