From: | John Meyer <john(dot)l(dot)meyer(at)gmail(dot)com> |
---|---|
To: | Raymond O'Donnell <rod(at)iol(dot)ie>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Male/female |
Date: | 2006-12-08 15:31:19 |
Message-ID: | 45798547.3050806@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
> rod(at)iol(dot)ie
> ----------------------------------------------------------------------
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2006-12-08 15:33:57 | Re: Male/female |
Previous Message | Raymond O'Donnell | 2006-12-08 15:23:11 | Male/female |