On 21 April 2013 12:17, Thomas Kellerer <spam_eater@xxxxxxx> wrote: > DB2 lets you define your own types (just as Postgres) but with the added > benefit that you can mark them such that they are _not_ comparable, e.g. to > avoid comparing "apples to oranges". Sounds like an interesting feature we might want, but you should discuss it on hackers. What does the SQL standard say about this? Is this actually useful for anything? I don't remember any complaints about the current behaviour. > As a type definition in Postgres can also include comparison functions, I > have the feeling that this should be possible, but I don't have an idea on > how to start to be honest. Postgres supports both domains and row types. So you can treat this as a row type with just one attribute. Look at make_row_comparison_op() in src/backend/parser/parse_expr.c If you can work out where to put it, you'd just need an if test to prevent the row comparison recursing into its component types. That would be stored on the pg_type catalog table as a boolean attribute, defaulting to current behaviour. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
