Re: Alias hstore's ? to ~ so that it works with JDBC
От | Merlin Moncure |
---|---|
Тема | Re: Alias hstore's ? to ~ so that it works with JDBC |
Дата | |
Msg-id | CAHyXU0yt2vJmdfRBJkNfNNCu6NHdPpi+Qd7y91JqU+aquqFNLg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Alias hstore's ? to ~ so that it works with JDBC (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Alias hstore's ? to ~ so that it works with JDBC
|
Список | 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 по дате отправления: