Second method might be better. Of course, you could also do a one chracter gender "M/F" if you want to save space.
Raymond O'Donnell wrote: > Just wondering.....how do list member represent gender when storing > details of people in a database? > > I've done it two ways: > > * A bool column, with the understanding that true/false represents > one gender or the other. > > * Create a domain, something like: > CREATE DOMAIN gender_domain > AS character varying(7) > NOT NULL > CONSTRAINT gender_domain_check CHECK ((((VALUE)::text = > 'male'::text) OR ((VALUE)::text = 'Female'::text))) > > I personally prefer the second, as it's self-documenting...is there > any other/better way of doing it? > > --Ray. > > > ---------------------------------------------------------------------- > > Raymond O'Donnell > Director of Music, Galway Cathedral, Galway, Ireland > [EMAIL PROTECTED] > ---------------------------------------------------------------------- > > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
