On 2017/12/07 12:20 PM, Silvio wrote:
When all open LOBs are transferred to the client side of the connection when the transaction is closed they can still be
read by the application afterwards. The only noticeable difference in behavior would be a potential performance hit and
memory consumption when closing the transaction (which could be compensated by faster reading of the LOBs after that).
It would not have to change application semantics.
But I might be oversimplifying things here. Please correct me if I am wrong.
That is doable, but has nasty performance surprises if you, for example, do SELECT * on a table with a LOB column. If
the LOB is big enough, it gets buffered to disk on the client side, and your SELECT performance is suddenly terrible.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
