On Thursday, 7 December 2017 12:24:10 UTC+1, Noel Grandin wrote: > > > 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. >
Does that mean that you allow reading the resultset AFTER the transaction completes? I was assuming the transaction closes when the resultset is closed (or at least the records had been fetched), and not before that. Therefore I was under the impression that the problem was limited to the case where someone has already done the getClob and then closes the transaction/resultset, while still holding on to the LOB-handle and reading it. That is why I considered it such a strange edge-case. -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
