On Wednesday, 6 December 2017 20:27:52 UTC+1, Noel Grandin wrote: > > Well, there is also the matter of not having enough time - it would be > fairly complex to get all the edge cases right. > > I think we all understand that you have limited time and resources, no argument there. I would just like to say that I currently consider MVStore unfit for production for these types of problems and therefore still use PageStore. Database growth beyond "actual content * some_reasonable_factor" is a problem. Database growth caused by reading is unacceptable. So from my point of view this is a show stopper with highest priority.
I wonder how you manage to efficiently facilitate read-only connections (which are about 90% in my case) when being forced to write once a LOB is encountered. Why not transfer all LOBs to the client at once during transaction closing when it does such a nonsensical thing as reading them after closing the transaction they where acquired in? -- 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.
