Re: Alias hstore's ? to ~ so that it works with JDBC
| От | Andrew Dunstan |
|---|---|
| Тема | Re: Alias hstore's ? to ~ so that it works with JDBC |
| Дата | |
| Msg-id | 51153B12.3000903@dunslane.net обсуждение исходный текст |
| Ответ на | Re: Alias hstore's ? to ~ so that it works with JDBC (Kris Jurka <books@ejurka.com>) |
| Ответы |
Re: Alias hstore's ? to ~ so that it works with JDBC
|
| Список | pgsql-hackers |
On 02/08/2013 12:41 PM, Kris Jurka wrote: > > On Fri, 8 Feb 2013, Dave Cramer wrote: > >> Would this be an postgresql specific escape sequence ? I don't think the >> spec allows for this does it ? >> > Yes, this would be a postgresql jdbc driver specific escape. The spec > doesn't have a concept of private escape sequences, but that doesn't seem > like the end of the world. Clearly the user here is writing postgresql > specific code to use hstore operators, so there's not a portability loss > here. > I assume, though, that you're not talking about something that's hstore-specific, but rather something that will allow the user to put a non-parameter question mark in the query string. As has been noted upthread, the hstore use is far from the only one that causes users to trip on this. cheers andrew
В списке pgsql-hackers по дате отправления: