[GRASS-user] getting from DBF to SQLite

[Michael Barton]

How can you change the default by changing the db.connect string? I'd like to do it.

I don't think it is all that difficult connecting tables across different vector objects, but agree (and said at the time) that it is probably a pretty rare occurrence in reality.

Michael
______________________________
C. Michael Barton 
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 	480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax:          480-965-7671(SHESC), 480-727-0709 (CSDC)
www: 	http://csdc.asu.edu, http://shesc.asu.edu
		http://www.public.asu.edu/~cmbarton

On Feb 14, 2013, at 2:59 PM, Hamish <hamish_b at yahoo.com>
 wrote:

> Michael wrote:
>> This and especially portability is why I argued--
>> unsuccessfully--
> 
> ? I thought the question was still up in the air for g7 and 
> for now it was user choosable by the way you constructed the
> db.connect string.
> 
>> for a separate sqlite DB for each vector file, even if it is
>> inefficient.
> 
> is it? only when doing joins? if so, how common a use case is
> that? (no idea how well sqlite handles fseeks() to jump right to
> the data it needs, or if it has to read in the whole file)
> 
> I'm mildly in favour of per-map dbs as I've often seen 600mb
> vector datasets on 32bit machines, and 2-4gb limit of the
> filesystem doesn't seem so far away if those get set to be
> cumulative. But I am fairly ignorant of DB issues and sqlite
> implementations in particular, so am not really familiar with
> what gains you might see from the monolithic approach.
> 
> 
> best,
> Hamish