From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Kris Jurka <books(at)ejurka(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 18:00:00 |
Message-ID: | CADK3HHLMLKB+qZ5dgAjYMxk_OJxz4T-06DNKUhu8uMF53v7shQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
That would seem to be the implication. JDBC wouldn't really know anything
about hstore.
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On Fri, Feb 8, 2013 at 12:51 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> 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 | Andreas Kretschmer | 2013-02-08 18:03:35 | Re: Bug, Feature, or what else? |
Previous Message | Josh Berkus | 2013-02-08 17:58:37 | Re: Considering Gerrit for CFs |