executeUpdate API contract. Return value equals 0.

From: Jeremy Whiting <jwhiting(at)redhat(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: executeUpdate API contract. Return value equals 0.
Date: 2013-02-26 13:15:20
Message-ID: 512CB568.70709@redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hi,
I have seen there have been conversations about the returned value from
executeUpdate when using partitioned tables. This thread places the
issue in the postgres-server court:

http://www.postgresql.org/message-id/013901c5fad9$1c18c600$ca78a8c0@yawin.yesasia.com

and another coversation on the pgsql-bugs mailing list that seems to
bat the problem back at the pgjdbc driver :)

I have written a test case for the driver and made it available on
GitHub. It is compatible with the current testsuit. It is there for you
to consider it's merits and use it if considered useful. I would like to
think it gives this issue visibility.

https://github.com/whitingjr/pgjdbc/tree/partitioned_table_test

Is the best way to progress this issue is to raise it again on
pgsql-bugs list ?

Regards,
Jeremy

--
Jeremy Whiting
Senior Software Engineer, Middleware Performance Team
Red Hat

------------------------------------------------------------
Registered Address: Red Hat UK Ltd, 64 Baker Street, 4th Floor, London. W1U 7DF. United Kingdom.
Registered in England and Wales under Company Registration No. 03798903. Directors: Michael Cunningham (USA), Mark Hegarty (Ireland), Matt Parson (USA), Charlie Peters (USA)

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Marc Fournier 2013-02-27 00:10:17 ENUM type via JDBC using connect string ...
Previous Message Michael Paquier 2013-02-25 04:16:10 Re: [JDBC] can't access through SSL