From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Mikko Tiihonen <mikko(dot)tiihonen(at)nitorcreations(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Patch: Add support for hstore extension - and map it to/from java.util.Map |
Date: | 2012-05-15 10:47:50 |
Message-ID: | CADK3HH+vK5Of4BR0XQf=R9xJuOtQtDttaRcUJypwtcG3eE5vTA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Mikko,
I have applied this patch to master, thanks!
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On Thu, May 10, 2012 at 5:17 AM, Mikko Tiihonen
<mikko(dot)tiihonen(at)nitorcreations(dot)com> wrote:
> Hi,
>
> Here is a patch to enable initial support for hstore in the jdbc driver.
>
> With the patch using ResultSet.getObject() on a hstore column and it returns
> a HashMap<String, String>
> Similarly a Statement.setObject(Map<Object,Object> will send the data to
> backend using hstore format.
>
> The patch supports both text and binary transfer modes. However the current
> patch does not automatically enable the faster binary transfer more, but
> instead user has to currently add binaryTransferEnable=<hstore-oid> to
> connection parameters.
>
> I'm still pondering how to enable the binary transfers automatically without
> the overhead of fetching the hstore oid on each connection startup.
> - can it be cached to some static cache based on connection url+login
> information?
> - if not then a way to lazy evaluate it needs to be implemented
>
> -Mikko
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
From | Date | Subject | |
---|---|---|---|
Next Message | Muhammad Altaf | 2012-05-15 10:59:46 | Re: Re: Issues with IN-OUT parameters for Array of Objects in EDB using Java |
Previous Message | Dave Cramer | 2012-05-15 10:25:50 | Re: Cleanup patch: Change from Vector/Hashtable to ArrayList/HashMap |