Thanks for the background Andrea - I was able to sort things out. It involved messing with uDig start up sequence a fair bit; you will find I added a method to your factory in order to perform a quick check; and based on the feedback manage to open a dialog letting the user know what is going it. Your code review/feedback would of course be welcome.
Jody On 16/08/2009, at 3:08 AM, Andrea Aime wrote: > Jody Garnett ha scritto: >> Thanks - I found that in the code base just now. What is more amazing >> to me is the *size* of the unpacked h2 database on disk. I am going >> to >> try and bundle it up in an eclipse plugin (where the result will be >> zipped up); but andrea is correct in that generating the database >> using the sql script is the most space efficient technique. HSQL was >> about 8 megs; H2 about 30 megs when "unpacked". > > Yes, it's a known issue of the current H2 storage format, there > is no way out, take it or leave it. > The H2 author is working on a more compact storage library (known > as the "page store") which is still considered to be experimental > thought: > http://www.h2database.com/html/changelog.html > Version 1.1.117 states "Various bugfixes and improvements in the > page store mechanism (still experimental). " > > Cheers > Andrea > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
