Re: Return Codes of BatchUpdateException in PostgreSql 9.6

Hi,

Can you provide a test case that reproduces the problem?

Vladimir

ср, 19 окт. 2016 г. в 12:24, Enrico Olivelli - Diennea <
enrico(dot)olivelli(at)diennea(dot)com>:

> Hi all,
> I recently updated my version of the JDBC driver in production.
>
> is it possible to release an hotfix ?
>
> thank you very much
>
> Enrico Olivelli
>
> Il giorno mar, 18/10/2016 alle 13.14 +0000, Tillmann Schulz ha scritto:
>
> Hi,
>
> After debugging my problem with the updateCount in the 9.4.1211 JDBC Driver I found the line in the code which causes the error.
>
> It's
>
> org.postgresql.jdbc.BatchResultHandler, Line 138 , JDBC Driver postgresql-9.4.1211
>
> @Override
> public void handleError(SQLException newError) {
> if (getException() == null) {
> Arrays.fill(updateCounts, committedRows, updateCounts.length, Statement.EXECUTE_FAILED); //138 <-- BUG
> //...
>
>
>
> Before the line "Arrays.fill..." the updateCounts contain the information of the already successfully inserted records [1,1,1,1,1,0,0,0,0,0].
> After filling the array with Statement.EXECUTE_FAILED the array contains [-3,-3,-3,-3,-3,-3,-3,-3,-3,-3]
> This is a not correct.
> The correct result is [1,1,1,1,1] or [1,1,1,1,1,-3]
>
> How to get this bug fixed? Can you rethink your implementation?
>
> Thank you for your help,
>
> Tillmann
>
>
>
> --
>
> Enrico Olivelli Software Development Manager @Diennea Tel.: (+39) 0546
> 066100 <+39%200546%20066100> - Int. 925 Viale G.Marconi 30/14 - 48018
> Faenza (RA) MagNews - E-mail Marketing Solutions http://www.magnews.it
> Diennea - Digital Marketing Solutions http://www.diennea.com
>
>
> ------------------------------
>
> Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed
> email marketing! http://www.magnews.it/newsletter/
>
> The information in this email is confidential and may be legally
> privileged. If you are not the intended recipient please notify the sender
> immediately and destroy this email. Any unauthorized, direct or indirect,
> disclosure, copying, storage, distribution or other use is strictly
> forbidden.
>