Re: proposal casting from XML[] to int[], numeric[], text[]

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: proposal casting from XML[] to int[], numeric[], text[]
Дата
Msg-id
6715.1194818342@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
proposal casting from XML[] to int[], numeric[], text[] "Pavel Stehule" <pavel.stehule@gmail.com>
Re: proposal casting from XML[] to int[], numeric[], text[] Peter Eisentraut <peter_e@gmx.net>
Re: proposal casting from XML[] to int[], numeric[], text[] "Nikolay Samokhvalov" <nikolay@samokhvalov.com>
Re: proposal casting from XML[] to int[], numeric[], text[] "Pavel Stehule" <pavel.stehule@gmail.com>
Re: proposal casting from XML[] to int[], numeric[], text[] "Nikolay Samokhvalov" <nikolay@samokhvalov.com>
Re: proposal casting from XML[] to int[], numeric[], text[] "Pavel Stehule" <pavel.stehule@gmail.com>
Re: proposal casting from XML[] to int[], numeric[], text[] Peter Eisentraut <peter_e@gmx.net>
Re: proposal casting from XML[] to int[], numeric[], text[] Andrew Dunstan <andrew@dunslane.net>
Re: proposal casting from XML[] to int[], numeric[], text[] Bruce Momjian <bruce@momjian.us>
Re: proposal casting from XML[] to int[], numeric[], text[] Bruce Momjian <bruce@momjian.us>
Re: proposal casting from XML[] to int[], numeric[], text[] "Nikolay Samokhvalov" <samokhvalov@gmail.com>
Re: proposal casting from XML[] to int[], numeric[], text[] "Pavel Stehule" <pavel.stehule@gmail.com>
Re: proposal casting from XML[] to int[], numeric[], text[] Tom Lane <tgl@sss.pgh.pa.us>
Re: proposal casting from XML[] to int[], numeric[], text[] "Nikolay Samokhvalov" <samokhvalov@gmail.com>
Re: proposal casting from XML[] to int[], numeric[], text[] Andrew Dunstan <andrew@dunslane.net>
Re: proposal casting from XML[] to int[], numeric[], text[] "Pavel Stehule" <pavel.stehule@gmail.com>
"Nikolay Samokhvalov"  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 по дате отправления
От: Pavel Stehule
Дата:
От: Josh Berkus
Дата:
FAQ