Page 1 of 1

Error showing content of blob with derby database

PostPosted: Thu Sep 24, 2015 8:30 am
by chme

Re: Error showing content of blob with derby database

PostPosted: Thu Sep 24, 2015 12:08 pm
by Serge
In Derby (and in some other databases) LOB content valid only during transaction life-time.
So if you want to work with LOBs in Derby you need to enable transactional mode (just toggle auto-commut button in main toolbar and refresh table contents).

Re: Error showing content of blob with derby database

PostPosted: Tue Sep 29, 2015 8:39 am
by chme

Re: Error showing content of blob with derby database

PostPosted: Tue Sep 29, 2015 11:36 am
by Serge
What DBeaver version and what Derby version do you use?
Embedded or Server?

Also could you post complete stacktrace of this error (you can get it in Error Log view)?

Thanks

Re: Error showing content of blob with derby database

PostPosted: Tue Feb 23, 2016 10:10 am
by chme

Re: Error showing content of blob with derby database

PostPosted: Tue Feb 23, 2016 5:42 pm
by Serge
You can't work with LOBs in auto-commit mode. You have to be in transactional mode. After switching into it just refresh table contents.

Re: Error showing content of blob with derby database

PostPosted: Wed Feb 24, 2016 8:11 am
by chme

Re: Error showing content of blob with derby database

PostPosted: Sun Feb 28, 2016 8:48 am
by Serge
Derby has some limitations in LOBs reading. If LOB value bigger than cache size (it depends on database - in my case it is 32kb) then LOB become invalid after statement close.
Workaround:
- Turn on preference Common->Result Sets->Keep open cursors in SQL editor
- Read LOBs from SQL editor (with SELECT .. FROM ..)

I'll add extra LOBs caching option in the next version.
Thanks for report.