With the speed of today's computers, and the tiny size of your database, speed isn't going to be an issue. Basically, you should write the cleanest code you can, to make maintenance simpler. Only after you have something and it proves to be too slow (which I don't expect to see in this case), do you look for optimizations.
I'm not advocating being purposefully wasteful...It's just that programmer time is much more expensive than computer time....
In reply to Re^3: Perl or Mysql to store multiple choices?
by roboticus
in thread Perl or Mysql to store multiple choices?
by punch_card_don
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |