[GRASS5] Re: sqlite browser

[Michael Barton]

Perhaps an environmental variable like SQL_BROWSER_PATH might be useful,
given that the name (on my Mac at least) is full of spaces and has an
embedded version number which will change with every update. Some kind of
find that could return the name and path the the browser could automate
this.

I have several other randomly related thoughts.

1. If we do use sqlite, we need a translation utility between dbf and
sqlite. 
2. We might want to have an "sql" directory in each mapset, like we do for
dbf. This would be the location for a default sqlite database for each
mapset, containing tables for each vector file. The default database could
simple carry the name of the mapset. This does not preclude the creation and
use of other sqlite database in other locations, of course.
3. GRASS would need to be able to create an empty sqlite database
automatically for each mapset, so that tables could be added as needed.

The browser could actually live inside the GRASS directory structure (e.g.,
$GISBASE/bin or somewhere else meaningful) if included, as it's not all that
big. In this case, it could be given a simple name like "sqlite_browser".
This might make the test you propose easier. It could also be a link to the
app in another location, but that might get more difficult.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Hamish <hamish_nospam at yahoo.com>
> Date: Sat, 12 Nov 2005 20:46:20 +1300
> To: Michael Barton <michael.barton at asu.edu>
> Cc: <grass5 at grass.itc.it>
> Subject: Re: [GRASS5] Re: sqlite browser
> 
>> I just tried this and it's very nice. If we switch to sqlite for the
>> default attribute database for GRASS, I'd strongly recommend finding a
>> way to include this as at least an optional add-on for GRASS. This
>> would solve the need for an attribute management interface.
> 
> Can anyone figure out how to run a test when d.m starts to see if
> HAVE_SQLITEBROW="`which sqlitebrowser`" works, and if not grey out the
> menu item for it? Then it could go into the menu and give people a hint
> about what they need to install to get the functionality.
> 
> 
> Hamish