Re: JDBC and positioned updates

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Hédi HACHENI <hacheni(at)kopileft(dot)com>
Cc: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: JDBC and positioned updates
Date: 2015-12-25 15:38:49
Message-ID: CAB=Je-F-j-XY6yZCZtcByWkRL+saNJ7rMZXuRovYtp2cP33XqA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

1) Have you considered using "updatable ResultSet"?

Here's a sample:
https://github.com/pgjdbc/pgjdbc/blob/32f513370306529005cb36d968f8e415f4a88aec/pgjdbc/src/test/java/org/postgresql/test/jdbc2/UpdateableResultTest.java#L301-L303

2) > WHERE CURRENT OF cursor_name

ResultSet implementation fetches result rows in batches, thus "current
of" at the database side might point to a slightly different row than
ResultSet at the java side.

3) You do not expect high throughput of that kind of API, do you?
Updatable ResultSet is not using batching, so each update would result
in a database roundtrip.

Vladimir

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Hédi HACHENI 2015-12-26 08:01:01 Re: JDBC and positioned updates
Previous Message Hédi HACHENI 2015-12-25 15:10:51 JDBC and positioned updates