Kevin Wooten wrote:
> > On Nov 4, 2014, at 12:55 AM, Craig Ringer wrote:
> >
> > I have to say I like some aspects of how pgjdbc-ng is being done - in
> > particular use of Maven and being built around non-blocking I/O.
> >
> > OTOH, the use of Google Guava I find pretty inexplicable in a JDBC
>
> On Nov 4, 2014, at 12:55 AM, Craig Ringer wrote:
>
> On 11/04/2014 07:56 AM, Mikko Tiihonen wrote:
>> I also think the async I/O is the way to go. Luckily that has already been
>> done
>> in the pgjdbc-ng (https://github.com/impossibl/pgjdbc-ng), built on top
>> of netty java NIO library. It
On 11/03/2014 07:05 AM, Scott Harrington wrote:
> This avoids the need for a Future, and avoids the client having to
> loop/sleep until done.
A Future is the logical way to represent an asynchronous operation in
Java. Why implement something else that doesn't fit into existing
libraries and tools
On 11/03/2014 07:05 AM, Scott Harrington wrote:
> I looked over your patch. Your list of ResultHandlerHolders seems to be
> the right direction, but as Tom Lane mentioned there may need to be some
> way to ensure the statements are all in the same transaction.
Why go down this track, when we alre
On 2014-11-01 14:04:05 +, Mikko Tiihonen wrote:
I created a proof of concecpt patch for postgresql JDBC driver that
allows the caller to do pipelining of requests within a
transaction. The pipelining here means same as for HTTP: the client
can send the next execution already before waiting fo
