Andrea Aime wrote:
so it seems we might need to reach an agreement on the embedded db to use.
I am +0 on H2 and -0 on JavaDB/Derby, on the basis of the devil we know,
and to reduce duplication.
I am not all that happy with H2. My attempts to fix a nasty EPSG
empty-/tmp fail-once unit test
Ben Caradoc-Davies ha scritto:
Andrea Aime wrote:
so it seems we might need to reach an agreement on the embedded db to
use.
I am +0 on H2 and -0 on JavaDB/Derby, on the basis of the devil we know,
and to reduce duplication.
I am not all that happy with H2. My attempts to fix a nasty
2009/6/11 Ben Caradoc-Davies wrote:
What does geotoolkit use? [*runs and hides*]
Dear me, you are a stirrer sometimes :-)
+1 for H2 (I've no problems with it being a solo effort at present)
+0 for JavaDB at some stage if demand and resources are there
Michael
Andrea Aime wrote:
Ben Caradoc-Davies ha scritto:
I am not all that happy with H2. My attempts to fix a nasty EPSG
[.. rambling anecdote ...]
You mean HSQL here? We're not using H2 for EPSG factories at the moment.
You are quite right. I must get more sleep. While H2 and HSQL share a
Michael Bedward wrote:
2009/6/11 Ben Caradoc-Davies wrote:
What does geotoolkit use? [*runs and hides*]
Dear me, you are a stirrer sometimes :-)
It's a talent.
But seriously, I hope one day we will reunite with the Lost Tribe of
GeoTools.
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
Hi, aware of the fact that I can't vote, I will anyway give my comment
(in case of an even, this might count as a 0.0001) :)
+1 for H2 for obvious JGrass reasons and because the indexes seems to
be not too far
+1 for spatialite whenever it will come
Ciao,
Andrea
On Wed, Jun 10, 2009 at 10:18
Another fact about Derby.
Derby is fully DB2 compatible (sql and jdbc) and you can switch easily to a
DB2 Community Edition which is the full powered db2 product without
clustering.
But I dont want to produce additional work and this is not an extremly
important question, so I will leave the
Voting is open to all developers :) So your +1 is welcome.
As for my vote, i am +1 on H2. But agree with Andrea that we should not
rule out a JavaDB version, what is one of the benefits of the
referencing plugin system. But if we have resources backing H2, then
let's go with H2.
andrea
