hamish_b at yahoo.com
Thu May 7 08:04:11 EDT 2009
> Probably we could move to SQLite in GRASS 6.5. Note there
> are still remaining bugs,
would there be any backwards-compatibility issues?
we would first have to fix those bugs and get the optional per-map|mapset bits ready before doing the change.
> > todo: for sqlite decide if we want per-map DB files
> > like with DBF or single DB file per mapset.
> I would vote for both approaches. User can decide what he
> prefers via environmental variable, e.g. GRASS_SQLITE_PER_MAPSET.
I think it would have to be a g.gisenv variable, or perhaps stored in
the $MAPSET/VAR file.
which way would be the default?
More information about the grass-dev