On fre, 2012-01-20 at 09:08 +0530, Nikhil Sontakke wrote: > > Umm, conisonly is set as false from primary key entries in > pg_constraint. > And primary keys are anyways not inherited. So why is the conisonly > field interfering in rename? Seems quite orthogonal to me.
In the past, each kind of constraint was either always inherited or always not, implicitly. Now, for check constraints we can choose what we want, and in the future, perhaps we will want to choose for primary keys as well. So having conisonly is really a good step into that future, and we should use it uniformly. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
