|> > I disagree. In several relations (views of the world) one |needs to have a |> > hand full of well defined values while |> > integers or bools are not appropriate and strings are too |free form. |> > For example male female or true and false. Whilst the |second has a well |> > known type, other things like a telephone number type |don't have such type. |> > So a new one should be created instead of (varchar/ xy |between 4 and 8). One |> > might argue that new 1:n relations with integrity shall be |established but |> > this is in my eyes overkill for a constant number of values. |> > Also think of schema export without data. These values are |part of the |> > schema data but not the schema itself which in this sense is wrong |> |> Please, most of this can be done with CHECK(...). | |Indeed. A CHECK constraint on a DOMAIN is an ENUM plus some.
Yea, that's what also I currently doing. But using varchars instead of symbolic values (as int4) is just more efficient. | |-- | | |---------------------------(end of |broadcast)--------------------------- |TIP 5: Have you checked our extensive FAQ? | | http://www.postgresql.org/docs/faq | ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
