> > This patch adds a "notice" at constraint creation time if the referential
> > integrity check is to be "costly", that is the comparison operator
> > involves some coercion.
> This is not the correct test at all.

You mean my morning 5mn programming will not be enough? ;-)

> The correct test would involve
> looking in pg_amop to see if the selected operator is a member of the
> opclass for the referenced column's index.  (IIRC there are helper
> functions in lsyscache.c that will make this easier.)

Ok, I'll have a look.

Fabien Coelho - [EMAIL PROTECTED]

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?


Reply via email to