"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> ... what I was wondering about is creating a
> 'type' that is a rollup for:
> - create parent table with int id field and text and indexes
> - add RI to base table
> - add triggers/views/rules/other glue to make the id field hidden and
> transparent to users in normal uses
Given the difficulties we've had with SERIAL columns, this seems much
less than trivial :-(. I'd be interested to see a good solution ---
I suspect it needs one or two ideas we haven't had yet.
In the meantime, I agree with Andrew's reply that the best stopgap is to
invent a bespoke datatype for each required ENUM set, with input and
output functions that have the list of values hardwired in.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
