Hi Ava,

This is almost certainly caused by the name of the H2 database file changing to include the version of H2 in the filename. This was in the course of upgrading H2 from 196 to 199 which required doing a dump and restore. The advantage of using the newer version is that the LOB expansion that caused countless Mango users to shrink their H2 databases manually and in some cases regularly has been fixed.

Currently the version is 199, so the filename is mah2-199.h2.db now. This means the connection URL needs to be modified to:

jdbc:h2:/opt/mango/databases/mah2.199

I think given this it would probably be in the module's interest to add a way to say it's this Mango's database, to avoid this issue if we update H2 again / it requires an actual upgrade path like 196 to 199 did.

Thanks for bringing this to our attention!

Oh yes, now I see that the problem happens only in the legacy UI, in the new datasource page UI, the feature is working properly!