| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Nicola Zanaga <NZanaga(at)efsw(dot)it> |
| Cc: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Slow performance updating CLOB data |
| Date: | 2016-07-18 10:34:20 |
| Message-ID: | CADK3HH+_S4MFsn0tb3-5fTJCjbqbuK18nmRB2F4Kt6BRw=ycFQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 18 July 2016 at 06:27, Nicola Zanaga <NZanaga(at)efsw(dot)it> wrote:
> 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 update CLOB 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
>
Well all drivers have to do something similar. Not all result sets are
updatable. What do other drivers do ?
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2016-07-18 11:48:09 | Re: Slow performance updating CLOB data |
| Previous Message | Nicola Zanaga | 2016-07-18 10:27:20 | R: Slow performance updating CLOB data |