Is needed a new db (version 1.4.184) or I can use the actual db? Because in that case I should copy all data from the actual db to the newer one...and I've the problem that the emailcontent table can't be copied.
Thanks very much 2015-01-14 18:06 GMT+01:00 Thomas Mueller <[email protected]>: > Hi, > > Could you append ";trace_level_file=3" to the database URL, then run your > test case against a new database (version 1.4.184), and then post the > resulting database and *.trace.db file? The test case should be minimal in > this case, so that the database doesn't get big (a few MB is enough for > this). And most importantly, the *.trace.db file should stay small (also > only a few MB). But still the test case should execute as much as possible > from your application. That should be enough to get one of those very small > (but not inlined) LOB values, and we can see what caused it. > > Regards, > Thomas > > > > On Wednesday, January 14, 2015, Daniele Renda <[email protected]> > wrote: > >> Ok, >> the only thing I do in my code is this: >> >> EmailContent emailContent = new EmailContent(); >> emailContent.setBody(testoEmail); >> emailContent.setEmail(email); >> entityManager.persist(emailContent); >> >> where "body" is a @Lob. So I don't do anything strange. I haven't the >> idea how I can make a test case to reproduce the problem. It is an hard >> challenge. >> >> 2015-01-14 10:44 GMT+01:00 Noel Grandin <[email protected]>: >> >>> >>> >>> On 2015-01-14 11:18 AM, Daniele Renda wrote: >>> >>>> Well, >>>> I'm using org.apache.tomcat.jdbc.pool.DataSource with Hibernate. So I >>>> never use Connection.createBlob / createClob but I >>>> don't know if then Hibernate do it internally. Make a reproducible test >>>> case is quite hard because the application is >>>> quite complex. >>>> I'm thinking if Sql logs would be useful for you.....what do you think? >>>> >>>> >>> Sorry, that's not particularly useful. Blobs are weird, and the API for >>> reading and writing them is also a little weird, so it's not hard to find >>> edge cases where things go wrong. >>> >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "H2 Database" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/ >>> topic/h2-database/ZVCOE0QErOo/unsubscribe. >>> To unsubscribe from this group and all its topics, 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. >>> >> >> >> >> -- >> Daniele Renda >> >> -- >> 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 a topic in the > Google Groups "H2 Database" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/h2-database/ZVCOE0QErOo/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- Daniele Renda -- 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.
