From: | Charles Pritchard <chuck(at)jumis(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: revisiting unix domain sockets |
Date: | 2014-01-20 23:51:57 |
Message-ID: | 52DDB69D.1000008@jumis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Here's a quick diff if anyone is interested.
https://gist.github.com/Downchuck/8531692
Needs JNA in the class path. Seems to work.
We've released this under the same license as pgjdbc.
https://github.com/pgjdbc/pgjdbc/blob/master/LICENSE
Uses ?unixSocket= as the parameter for the path.
-Charles
On 12/17/2013 4:25 AM, Dave Cramer wrote:
> Send a PR and I'll look at it.
>
> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca
>
>
> On Tue, Dec 17, 2013 at 6:01 AM, Charles Pritchard <chuck(at)jumis(dot)com
> <mailto:chuck(at)jumis(dot)com>> wrote:
>
> Has there been any movement and-or push back around supporting
> unix domain sockets within the connection string? I've seen simple
> patches on the web to add support- it seems like a trivial matter,
> is there a design consideration or other issue outstanding?
>
> Example of using JNA for unix domain sockets:
> http://www.productivity.org/projects/mysqlunixsocket/MysqlUnixSocketFactory.java
>
> -Charles
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org
> <mailto:pgsql-jdbc(at)postgresql(dot)org>)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Whiting | 2014-01-22 11:04:48 | Master branch compile error using 1.5 spec. |
Previous Message | Stephen Nelson | 2014-01-20 14:07:53 | Re: StringBuffer vs. StringBuilder |