Re: Versioning policy PgJDBC - discussion - Mailing list pgsql-jdbc

From Brad DeJong
Subject Re: Versioning policy PgJDBC - discussion
Date
Msg-id F8F0ED16CB59F247B7EFD0E1DB34BC1F5CB5AA30@USALWEXMBX3.infor.com
Whole thread Raw
In response to Re: Versioning policy PgJDBC - discussion  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
Responses Re: Versioning policy PgJDBC - discussion
Re: Versioning policy PgJDBC - discussion
List pgsql-jdbc
Vladimir wrote:
> Well, current milestone has slipped a bit
> https://github.com/pgjdbc/pgjdbc/milestones, however there are just a
> couple of issues due.
> https://github.com/pgjdbc/pgjdbc/pull/690 "executeBatch vs
> serverprepared=0" -- needs review
> https://github.com/pgjdbc/pgjdbc/pull/611 "feat: allow byte[] and String to
> be accessed as .getLob, and .getClob" -- test should be reviewed (e.g.
> assert messages added)

I read this as a request for assistance in reviewing these pulls. I looked over the byte[]/Blob part of pull 611 (PgByteaBlob and PgByteaBlobTest) and submitted comments. AbstractBasicLob and PgResultSet changes look good. I did not look over the String/Clob part yet.

pgsql-jdbc by date:

Previous
From: Brad DeJong
Date:
Subject: Re: Versioning policy PgJDBC - discussion
Next
From: Dave Cramer
Date:
Subject: Re: Versioning policy PgJDBC - discussion