[GRASS5] Re: question about sqlite

[Daniel Calvelo Aros]

Indeed, it is important to support the format. 

What I think Glynn had in mind is not accessing DBF files through a GRASS DBMI
driver but rather convert them to SQLite (and back, eventually) and not bother
anymore about parsers, SQL and the lot.

I'd say yes, let's build converters between DBF and sqlite3 files (and also
between txt/csv formats and sqlite3) and drop sqlp, since the equivalent in
SQLite is much better and powerful. As an aside, deprecate DBF and propose
sqlite3 as the default storage format, starting from (say) 6.2.

That would mean having GRASS depend on sqlite, of course.

-- Daniel Calvelo Aros

---------- Original Message -----------
From: Michael Barton <michael.barton at asu.edu>
To: Glynn Clements <glynn at gclements.plus.com>, Radim Blazek
<radim.blazek at gmail.com>
Cc: grassdev <grass5 at grass.itc.it>
Sent: Wed, 19 Oct 2005 10:54:42 -0700
Subject: Re: [GRASS5] Re: question about sqlite

> DBF is a widely used, standard format--in spite of being old and 
> klunky. It can be imported or read by a wide variety of other 
> programs (e.g., Open Office, Excel, Access, Filemaker). It is also 
> the standard table format for ESRI, MapInfo, and Idrisi. It would be 
> very inconvenient to drop it.
> 
> Michael
> ______________________________
> Michael Barton, Professor of Anthropology
> School of Human Evolution and Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA
> 
> voice: 480-965-6262; fax: 480-965-7671
> www: http://www.public.asu.edu/~cmbarton
> 
> > From: Glynn Clements <glynn at gclements.plus.com>
> > Date: Wed, 19 Oct 2005 17:56:04 +0100
> > To: Radim Blazek <radim.blazek at gmail.com>
> > Cc: Michael Barton <michael.barton at asu.edu>, grassdev <grass5 at grass.itc.it>
> > Subject: Re: [GRASS5] Re: question about sqlite
> > 
> > 
> > Radim Blazek wrote:
> > 
> >>> Could you give me a quick overview of what it means to compile GRASS with
> >>> sqlite? Here are a couple questions I have.
> >>> 
> >>> 1) Is it simply a driver that lets GRASS recognize a database/table created
> >>> by sqlite in an active sqlite session started in another process, like a
> >>> Postgresql table in an active Postgresql session?
> >>> 
> >>> 2) Does it/can it active an sqlite session from within GRASS?
> >>> 
> >>> 3) Are there other features that I'm not asking about that I should know?
> >> 
> >> The sqlite driver works like any other db driver (dbf, pg, mysql, odbc).
> > 
> > With the addition of SQLite, is there any reason to continue to
> > support the DBF driver?
> > 
> > -- 
> > Glynn Clements <glynn at gclements.plus.com>
> 
> _______________________________________________
> grass5 mailing list
> grass5 at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass5
------- End of Original Message -------