Hi, I think this is related to LOB (BLOB and CLOB) handling. I am working on that, I have identified one case already. A simple, reproducible test case would help however (if possible with just JDBC and without JPA), even thought it is not urgent. Or maybe you can test it using a nightly build, after I have fixed the known issue. I will let you know.
Regards, Thomas On Tue, Sep 29, 2015 at 2:57 PM, Laurane Varrailhon < [email protected]> wrote: > I forgot to mention that we to access to data with JPA. > > > > Le lundi 28 septembre 2015 16:47:45 UTC+2, Laurane Varrailhon a écrit : >> >> Hi everybody, >> >> >> I have recently faced the problem of abnormal size of the database. After >> a total purge of database, the database size did not shrinking (2 Go). >> Since the 1.4.186 version, the problem is solved, but I have to close and >> re-open database to see the database shrinkage (from 2 Go to 100 Ko). This >> action is not really an option in production context. >> I would like to know if it is possible to bypass this, in reproducing the >> behavior that triggers the reduction of the database size when the >> connection is already opened. >> >> >> Thank you in advance. >> > -- > 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 http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
