On Thu, 2023-08-03 at 04:27 -0700, Thomas Hurley wrote: > I am a Product Manager with 3 commercial products using H2 and > needing to upgrade. 1 upgraded to 2.1 and we had to go through a > migration process to make this seamless to our customers (mostly > heavily regulated companies). This upgrade went ok and no major > issues but we invested a lot of engineering time to make sure that > worked well for all upgrading customers. > > It now looks like upgrading from 2.1 to 2.2 will require the same > effort. Is that the case? Are you planning to make updates backward > compatible or will every upgrade require scripting to migrate data - > this is not a feasible solution for me and ask that you make upgrades > backward compatible to avoid your customers (and mine) having to > customise migration every version upgrade of H2. > > Look forward to your response.
Greetings! We are in a similar situation, having multiple H2 Databases on our servers and need to upgrade all of those smoothly when we deploy newer versions of our software. Also, NOT upgrading H2 is never really an option since all the provided fixes are valuable and needed. That's why we wrote the Migration Tool. It can convert whole (recursive) directories with all DBs in it and we integrated it directly into our software. Upgrading from 2.1 to 2.2 was a minor task for us. We did not notice any incompatible features. Biggest issue (for us) is that CTEs are completely broken since 2.1.212 and return no rows (without throwing errors). As long as you don't use CTEs, you should be good. If you use CTEs you may need to refactor your queries (We use JSQLParser for this.) Good luck and cheers Andreas -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/f87230f862e9a93456bae210c8c8bab7a68a2086.camel%40manticore-projects.com.
