sqlite and grass65: was Re: [GRASS-dev] sqlite and grass64

Markus Neteler neteler at osgeo.org
Thu Mar 5 13:04:46 EST 2009

On Thu, Mar 5, 2009 at 4:38 PM, Moritz Lennert
<mlennert at club.worldonline.be> wrote:
> On 05/03/09 10:43, Markus Neteler wrote:
>> Suggestion:
>> make SQLite as default DBMS driver in devel_branch6 (alias GRASS 6.5).
>> Since today, in 2009, the driver has received a lot of testing, is
>> definitely superiour to DBF (where we regularly get complaints).
> +1
>> If allowing one file per map isn't too hard to implement as optional
>> feature it might be a (last) requirement to make it the default driver.
> I think that for the same arguments as those brought forward by Glynn above,
> we should make single file db the default. Anyone who really needs it can
> easily create a per-vector db with v.db.connect.

Remember that Glynn mentioned that joins won't work in this case.

> Concerning the need to be able to easily backup/share, I think we definitely
> need some module which isolates and exports a series of chosen maps in a new
> temporary mapset with a local sqlite db file, copies the chosen maps into
> this temp mapset and then creates a tarball (or zip or whatever) with the
> basic LOCATION info (i.e. a PERMANENT mapset with PROJ and WIND files) and
> the temp mapset. Shouldn't be too hard to wip up, or ?

Essentially a v.pack/v.unpack, right?


More information about the grass-dev mailing list