From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | 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 16:48:50 |
Message-ID: | CADK3HHLY2bzumJvVx6dxKNVqdrT-ExX2bNjNsnFLuTXyR-yPeQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 8, 2013 at 11:43 AM, Kris Jurka <books(at)ejurka(dot)com> wrote:
>
>
> On Wed, 6 Feb 2013, Seamus Abshere wrote:
>
> > I personally don't know of any way around the conflict except changing
> > JDBC or hstore, and I don't think JDBC is gonna change.
> >
>
> I think changing JDBC is the way to go. Currently JDBC supports escape
> sequences for cross database portability and it seems reasonable to
> support an escape sequence that allowed passing ? to the backend instead
> of interpreting it as a parameter. This will be more complicated than you
> might hope because the escape processing currently happens prior to bind
> parameter detection so I'm not sure what a good patch would really look
> like, but given the feedback provided here, it's worth investigating.
>
> Kris Jurka
>
> Would this be an postgresql specific escape sequence ? I don't think the
spec allows for this does it ?
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2013-02-08 16:55:30 | Re: Too frequent checkpoints ? |
Previous Message | Kris Jurka | 2013-02-08 16:43:26 | Re: Alias hstore's ? to ~ so that it works with JDBC |