Can you please elaborate on this? "Because using version 1.3.176 could have changed the database file already"
What could be changed by v176 that could cause incompatibilities with v169? On Wednesday, January 14, 2015 at 6:47:38 AM UTC, Thomas Mueller wrote: > > Hi, > > I can't say what the problem might be, but reverting to 1.3.169 should be > possible. But it might make sense to re-create the database, by first > creating a SQL script, then dropping the database, and re-creating it from > the SQL script. Because using version 1.3.176 could have changed the > database file already. > > > avoiding the creation of the TRACE FILE has absolutely nothing to do > with this problem > > I agree. > > Regards, > Thomas > > On Mon, Jan 12, 2015 at 2:07 AM, marcolopes <[email protected]> wrote: > >> We are experiencing too many problems with version 1.3.176 (latest stable >> 1.3 release). >> >> *Is there anything we should be aware of before downgrading to 1.3.169*? >> (we never experienced many problems with this version, used over a YEAR >> with thousands of installations of the same software). >> >> -- >> 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.
