Because it means moving to the new database format. If I just plug in 1.2.135 it simply won't read the existing databases.
I'd have to arrange for each installation to be converted, then (apart from the hassle) there would be no going back. In any case 1.2.135 is much too recent for me to be confident that it's really stable. I'd prefer other people to find the bugs, to be honest about it. My confidence in H2 regression testing has been somewhat shaken of late. On May 24, 11:35 am, Wildam Martin <[email protected]> wrote: > On Mon, May 24, 2010 at 10:50, Soupdragon > > <[email protected]> wrote: > > We've been using an old version for about 4 years now and obtained > > reasonable stability. Recently I, rather rashly as it turns out, > > decided to move us to a more recent version, which happened to be > > 1.1.107. It's been a bit of a disaster, compounded by the coincidence > > of a lot of database changes at the same time the upgrade went out. > > When you decide to upgrade - why not to the most recent one? 1.1.107 > is already quite old. It was mentioned by somebody that probably > 1.1.135 is the most stable currently. > - > Martin Wildam > > -- > You received this message because you are subscribed to the Google Groups "H2 > Database" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/h2-database?hl=en. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
