Re: Alias hstore's ? to ~ so that it works with JDBC

merlin,

I appreciate your perspective and wish that JDBC didn't present this 
problem. Still, with the rapidly growing adoption of both Postgres and 
JVM-based languages (thanks Heroku!) - plus the special power of hstore 
- I think it would be a shame if such a small accommodation could not be 
made.

Other hackers,

What is your take?

Best,
Seamus

PS. Switching to the EXIST() or DEFINED() functions is not, in my 
opinion, a solution because they can't use hstore's GiST or GIN indexes.

On 2/6/13 11:34 AM, Merlin Moncure wrote:
> The point is that Postgres should not introduce language constraints
> because of broken driver technology.  To move forward in your
> particular case, consider:
> *) switching to 'hstore defined()' function:
> *) hacking pg_operator (carefully look up and change oprname for the
> specific hstore operator)