Noel, can you elaborate a bit why reading LOBs results in writes to the database? Is it because the LOB content is copied somewhere in the DB so that the client does not need to keep transaction open to access LOB content? If that's the reason then I don't see how the ballooning could be prevented at all since you'll have to keep the LOB copy till the DB close.
I second Silvio's proposal, there should be a setting allowing to break backward compatibility, if that backward compatibility is the holdout in trying to resolve the issue. -- 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.
