+1 I have never actually had any issue with upgrading H2 and supporting databases created with older versions. Thomas seems pretty good about backward compatibility.
Indeed an upgrade works well for me. I want to start doing some h2 benchmarks with H2 and would like to work with the latest and greatest. -Justin On 10-06-22 2:14 AM, Gabriel Roldan wrote: > Hi all and sorry for cross-posting. > > I'd like to propose upgrading the version of h2database in the trunk > poms (both geoserver and geotools) to a newer version than the one > currently used. > > Situation is we've inadvertently been shipping geoserver with two h2 > jars, h2-1.1.104.jar and h2-1.1.119.jar. The former used by geotools and > geoserver, the later carried over as a transitive dependency from > geowebcache. > > I just discovered the problem while updating geoserver trunk to point to > geowebcache snapshot and got a compile error, since gwc now uses some h2 > connection pooling with some speed up benefits. > > Having talked to Andrea and Arne, we've seen that the h2 database format > doesn't change between those two versions, so, provided y update the > poms on both trunks to use 1.1.119 instead of 1.1.104 and the build > doesn't break, can I commit the version upgrade? any concern? > > TIA, > Gabriel > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
