Re: Constraint Type Coercion issue? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Constraint Type Coercion issue?
Date
Msg-id 7532.1126733322@sss.pgh.pa.us
Whole thread Raw
In response to Re: Constraint Type Coercion issue?  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: Constraint Type Coercion issue?
List pgsql-hackers
Martijn van Oosterhout <kleptog@svana.org> writes:
> How much discussion has there been on this?

None yet; I had a few half-baked ideas but nothing worth presenting to
the list.

> To some extent, collate
> implies a sort of parameterised operator class...

Hmm.  But an index couldn't support more than one collation order
AFAICS.  It'd probably make more sense to create operators and an
operator class for each collation you want to support; the mapping
to a call of a common support function would be embedded inside the
operator definition.  Otherwise we have to pass around an additional
parameter through an awful lot of places...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Constraint Type Coercion issue?
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Constraint Type Coercion issue?