| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Seamus Abshere <seamus(at)abshere(dot)net>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Alias hstore's ? to ~ so that it works with JDBC |
| Date: | 2013-02-08 17:51:14 |
| Message-ID: | 51153B12.3000903@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2013-02-08 17:52:33 | Re: DROP OWNED BY fails to drop privileges granted by non-owners (was Re: [GENERAL] Bug, Feature, or what else?) |
| Previous Message | Fujii Masao | 2013-02-08 17:46:54 | Re: [PATCH] pg_isready (was: [WIP] pg_ping utility) |