Thanks for the quick replies.
I'm using updateable resultset only to update CLOB data.
My application uses many databases. This method can be used with many driver (I think this is the "standard" mode to
updateCLOB data).
I took a look at the code in PgResultSet, and I think the driver will be slow with any operation on updateable
resultset,because it will always call " isUpdateable()" to do any operation.
So, in my opinion, this makes updateable resultset quite useless
To check if the query is updateable, the code first checks if it's using a single table, so should be easy to cache
tableand primary keys.
-----Messaggio originale-----
Da: pgsql-jdbc-owner@postgresql.org [mailto:pgsql-jdbc-owner@postgresql.org] Per conto di Vladimir Sitnikov
Inviato: lunedì 18 luglio 2016 10:54
A: Thomas Kellerer; pgsql-jdbc@postgresql.org
Oggetto: Re: [JDBC] Slow performance updating CLOB data
Is there a reason of using updateable resultset?
Simple update table set... should work just fine.
PS. Having table -> PK cache in pgjdbc would be good.
Vladimir
--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc