Re: JDBC and positioned updates
| От | Vladimir Sitnikov |
|---|---|
| Тема | Re: JDBC and positioned updates |
| Дата | |
| Msg-id | CAB=Je-F-j-XY6yZCZtcByWkRL+saNJ7rMZXuRovYtp2cP33XqA@mail.gmail.com обсуждение исходный текст |
| Ответ на | JDBC and positioned updates (Hédi HACHENI <hacheni@kopileft.com>) |
| Ответы |
Re: JDBC and positioned updates
|
| Список | 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
В списке pgsql-jdbc по дате отправления: