Skip site navigation (1) Skip section navigation (2)

Re: Question on simulating Enum Data type

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Morgan Kita" <mkita(at)verseon(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Question on simulating Enum Data type
Date: 2005-03-18 02:58:15
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
"Morgan Kita" <mkita(at)verseon(dot)com> writes:
> However, I am a little concerned about performance in that case. If I
> use domain constraints and keep the choices as strings then a string
> comparison will be done whenver I query on this field right?

Hm?  A domain constraint would cost cycles when storing into the table,
but not when querying it.  Joining to another table, on the other hand,
will cost you during queries.

If the strings are long, so that the amount of extra space involved adds
up to a lot, it'd probably make sense to go with integer codes.  But if
they're just a word or so then I'd lean to keeping it simple.

			regards, tom lane

In response to

pgsql-novice by date

Next:From: CimaDate: 2005-03-18 04:35:43
Subject: Reference and arrays
Previous:From: Michael GlaesemannDate: 2005-03-18 02:39:46
Subject: Re: Question on simulating Enum Data type

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group