Re: Alias hstore's ? to ~ so that it works with JDBC - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Alias hstore's ? to ~ so that it works with JDBC
Date
Msg-id CAHyXU0yt2vJmdfRBJkNfNNCu6NHdPpi+Qd7y91JqU+aquqFNLg@mail.gmail.com
Whole thread Raw
In response to Re: Alias hstore's ? to ~ so that it works with JDBC  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Alias hstore's ? to ~ so that it works with JDBC  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
On Wed, Feb 6, 2013 at 12:00 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
>
> On 02/06/2013 12:34 PM, Merlin Moncure wrote:
>>
>>
>> The point is that Postgres should not introduce language constraints
>> because of broken driver technology.
>
>
> +1
>
>
>> To move forward in your
>> particular case, consider:
>> *) switching to 'hstore defined()' function:
>
>
> good solution - but just use the existing "exist()" function.
>
>
>> *) hacking pg_operator (carefully look up and change oprname for the
>> specific hstore operator)
>
>
> bad solution. Why not just provide an additional operator?
>
>    CREATE OPERATOR ~ (
>         LEFTARG = hstore,
>         RIGHTARG = text,
>         PROCEDURE = exist,
>         RESTRICT = contsel,
>         JOIN = contjoinsel
>    );

yeah, this is much less hacky way to go.

merlin



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: JSON NULLs
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Fast promote mode skips checkpoint at end of recovery.