Re: setObject(...) with native Java arrays like String[] ?

To be candid, I need help managing the patches.

Many times the patches come in without test cases or without
documentation. All of these things require me to spend time I don't
have.

Also many patches or requests are very specific "itches" which solve a
particular problem for the submitter. Every new feature adds
complexity and possibly negatively effects performance.  It is useful
to keep in mind that the driver is used by lots of other people who
will not benefit from this particular feature request.


So I am open to suggestions as to how to manage this better. I know
that the main postgresql project has a system where other people
review patches. This seems like it is a good idea.

Notionally someone other than the submitter would review the patch.

Thoughts ?

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca


On Thu, Aug 23, 2012 at 3:47 AM, John Lister <john.lister@kickstone.com> wrote:
> On 23/08/2012 02:32, Craig Ringer wrote:
>>
>> I don't remember seeing the patch, actually.
>>
>> http://www.postgresql.org/search/?m=1&q=John+Lister&l=19&d=365&s=d
>>
>> The Pg mailing list manager is irritatingly good at eating messages with
>> attached patches, so it's possible nobody ever saw it.
>
> Odd, I remember getting the copy from the list, but not to worry, I've added
> a couple of tests and waiting while they run, will then repost it.
>
> John
>
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc