On Tue, Mar 8, 2011 at 5:51 PM, Steve Atkins
<steve@blighty.com> wrote:
tsvector or intarray might be other options, depending on how you're going to query it and whether those are really strings or more enum-ish.
The more SQLy way of doing it would be to have that stored in a separate table, with a foreign key to this one.
Using a separate table is what I've got now in an experimental conversion. This works well enough and might save me the bother of an enum update. Perhaps I should just move on.
Thanks Steve.
-Reece
