WE use XML here to store the values, however our requirements also add the
ability to use mutiple languages so its a little more complex.
For personal projects I store the various data like this into a
system_option table as text (1,Male;2,Female;) and then have a common
routine that grabs the
We have 0/1/2 for gender but also have tlkpSex or something like that. It
has the id and the string we want to use, then our queries just make sure
that data.gender=tlkpSex.gender.
Good luck!
Natalie
On 11/7/06, Tony Grimes <[EMAIL PROTECTED]> wrote:
Why not build the options into your data
Why not build the options into your data model? Instead of using integers
for gender, use a varchar field that stores 'Male' and 'Female'. You can
ensure data integrity by adding a check constraint to the column.
If the presentation might change depending on context, you can create gender
referenc
