On Wed, Dec 12, 2007 at 12:28:37PM -0800, pilzner wrote: > thats what I'm familiar with" discussion, just to get a feel of why its done > that way, if I'm doing anything wrong, or if there is an accepted way to > lock it down.
It'd be easy to lock down with a trigger that RAISEs ERROR in case OLD.id !=
NEW.id.
A
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
