Storing sex (gender) in database

by

There is already an ISO standard for this; no need to invent your own scheme:

http://en.wikipedia.org/wiki/ISO_5218

Per the standard, the column should be called “Sex” and the ‘closest’ data type would be tinyint with a CHECK constraint or lookup table as appropriate.

More Related Contents:

  1. how to create this table in sql server?
  2. Recommended SQL database design for tags or tagging [closed]
  3. Subqueries vs joins
  4. SQL – How to store and navigate hierarchies?
  5. Database design for a survey [closed]
  6. Strings as Primary Keys in SQL Database [closed]
  7. Custom SERIAL / autoincrement per group of values
  8. Safely rename tables using serial primary key columns
  9. What mysql database tables and relationships would support a Q&A survey with conditional questions? [closed]
  10. single fixed table with multiple columns vs flexible abstract tables
  11. Primary key or Unique index?
  12. Is there ever a time where using a database 1:1 relationship makes sense?
  13. DB design to use sub-type or not?
  14. How to design a database for User Defined Fields?
  15. Facebook database design?
  16. Composite Primary key vs additional “ID” column?
  17. Max length for client ip address [duplicate]
  18. What are the principles behind, and benefits of, the “party model”?
  19. Can I set ignore_dup_key on for a primary key?
  20. Should I use SQL_Variant data type?
  21. Postgres constraint for unique datetime range
  22. Which datatype should be used for currency?
  23. MySQL – how to front pad zip code with “0”?
  24. Composite Primary Keys : Good or Bad?
  25. What does ON [PRIMARY] mean?
  26. What is the best way to implement soft deletion?
  27. Is there a severe performance hit for using Foreign Keys in SQL Server?
  28. How important are lookup tables?
  29. Historical / auditable database
  30. Designing SQL database to represent OO class hierarchy

Leave a Comment