Re. the missing functionality of DBF, would it be feasible
for v.db.join to import the DBF table to a temp SQLite file,
do the join and export it back to a DBF?
Would the same thing be possible for other SQL ops that DBF
does not support? For where=SQL module options?
It should be possible to ship
On 06/03/09 01:24, Moskovitz, Bob wrote:
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 th
On 05/03/09 19:04, Markus Neteler wrote:
On Thu, Mar 5, 2009 at 4:38 PM, Moritz Lennert
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
defi
Markus Neteler wrote:
> 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.
AFAICT, there are two obvious ways to do this:
1. Have two SQLite drivers, one using a single file, the other using
one file per
On Mar 5, 2009, at 5:44 PM, wrote:
Date: Thu, 5 Mar 2009 16:24:38 -0800
From: "Moskovitz, Bob"
Subject: RE: sqlite and grass65: was Re: [GRASS-dev] sqlite and
grass64
To: "Markus Neteler" , "Moritz Lennert"
Cc: GRASS developers list
Mes
On Mar 5, 2009, at 5:44 PM, wrote:
Date: Thu, 5 Mar 2009 19:04:46 +0100
From: Markus Neteler
Subject: Re: sqlite and grass65: was Re: [GRASS-dev] sqlite and
grass64
To: Moritz Lennert
Cc: GRASS developers list
Message-ID:
<86782b610903051004n5601199ax269f60f194
> > 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 (o
On Thu, Mar 5, 2009 at 4:38 PM, Moritz Lennert
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 w
On 05/03/09 10:43, Markus Neteler wrote:
Coming back to an old thread:
(SQLite as default DBMS driver)
On Mon, Jan 14, 2008 at 12:55 AM, Glynn Clements
wrote:
Hamish wrote:
Are there any instances where the dbf driver can do some
functionality that the sqlite driver cannot? I use the sqlite
On Mar 5, 2009, at 3:43 AM, 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).
If allowing one file per ma
>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).
>
>
>Markus
+1. I think it's a great idea.
~ Eric.
___
Hi,
2009/3/5 Markus Neteler :
[...]
> 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).
>
> If allowing one file per map isn't too hard to
Coming back to an old thread:
(SQLite as default DBMS driver)
On Mon, Jan 14, 2008 at 12:55 AM, Glynn Clements
wrote:
> Hamish wrote:
>
>> > Are there any instances where the dbf driver can do some
>> > functionality that the sqlite driver cannot? I use the sqlite driver
>> > all the time for my
13 matches
Mail list logo
