On Thursday, 7 December 2017 10:33:36 UTC+1, Noel Grandin wrote: > > > Backwards compatibility is important to us, and the H2 code has worked > this way since I started working on it. >
I totally agree backward compatibility is important. That is why I opted for a (connection/database) setting or, if keeping two modes in the code would complicate things too much, a modified behavior which should be backward compatible. 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. -- 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.
