Re: proposal casting from XML[] to int[], numeric[], text[] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: proposal casting from XML[] to int[], numeric[], text[]
Date
Msg-id 6715.1194818342@sss.pgh.pa.us
Whole thread Raw
In response to Re: proposal casting from XML[] to int[], numeric[], text[]  ("Nikolay Samokhvalov" <samokhvalov@gmail.com>)
Responses Re: proposal casting from XML[] to int[], numeric[], text[]
List pgsql-hackers
"Nikolay Samokhvalov" <samokhvalov@gmail.com> writes:
> Alternative (and maybe better) approach would be:
>  - create comparison functions that work in the same way as string
> comparison functions do (currently, it's straight forward since XML is
> stored as string);
>  - do NOT create comparison operators to avoid explicit comparing XML values
> (to follow standard ways to work with XML and to avoid possible unexpected
> behaviors);
>  - create opclass based on these functions and, therefore, obtain GIN
> indexes support for xml[];

I'm not clear on what you're proposing.  There is no such thing as an
opclass with no operators (or at least, not a useful one), so this seems
mutually contradictory.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: proposal casting from XML[] to int[], numeric[], text[]
Next
From: Josh Berkus
Date:
Subject: Re: [hibernate-team] PostgreSQLDialect