From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | rodrigo(dot)sakai(at)zanthus(dot)com(dot)br |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: RES: Creating a new type |
Date: | 2006-06-29 13:47:00 |
Message-ID: | 20097.1151588820@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
"Rodrigo Sakai" <rodrigo(dot)sakai(at)zanthus(dot)com(dot)br> writes:
> So, I have to guarantee that this situation doesn't occur! But I don't
> want to use triggers because this check must be done on almost all tables
> that uses the type:
The fact that you don't want to do it doesn't make it the wrong
solution ;-)
At the moment there is no other way than a trigger. There's been some
speculation about whether GIST indexes could be extended to enforce
conditions like "no overlapping values in this column" (as a
generalization of the concept of unique indexes). No one's tried to
make that happen, though.
BTW, you might want to look at the "timetravel" code in contrib/spi/
... it's a tad old and crufty, but it sounds like you are trying to do
something pretty similar to that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rodrigo Sakai | 2006-06-29 17:47:48 | RES: RES: Creating a new type |
Previous Message | Rodrigo Sakai | 2006-06-29 12:38:17 | RES: Creating a new type |