That still puts the responsibility on the individual datatype author to
get it right. The case I'm most worried about is user-written datatypes
that are never going to magically acquire such asserts.
It seems to me that working with two assumption (binary equal and
catalog-defined equal function) in the same time is a wrong way. If we decide to
use binary equal criteria, then why we need catalog-defined equal at all? If we
use catalog-defined one, why we should require binary equality? Using both way
in the same time is an error prone. It's possible to say that two value is equal
if they are binary the same, if not - we should find catalog-defined equal
operation and call it. Binary comparison is only an optimization.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
