Re: executeUpdate API contract. Return value equals 0.
От | Craig Ringer |
---|---|
Тема | Re: executeUpdate API contract. Return value equals 0. |
Дата | |
Msg-id | 513033BC.3080203@2ndquadrant.com обсуждение исходный текст |
Ответ на | executeUpdate API contract. Return value equals 0. (Jeremy Whiting <jwhiting@redhat.com>) |
Ответы |
Re: executeUpdate API contract. Return value equals 0.
|
Список | pgsql-jdbc |
On 02/26/2013 09:15 PM, Jeremy Whiting wrote: > 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 :) Really? I either didn't see that thread or forgot it. Link? I don't see how PgJDBC can return rowcounts when trigger-based partitioning doesn't produce them. > > 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 The test case looks reasonable to me at a quick scan; haven't merged and run it yet. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-jdbc по дате отправления: