[GRASS-dev] v.in.ogr broken (\w shp)

[Michael Barton]

This no more limiting than we have now, but with a more robust database and
SQL.

These issues are the same if we use PostgreSQL or MySQL too.

I'm assuming that there is a way to export a table from an SQLite database
and import it into another one. If so, they people who wanted to do joins
could make a database where it is possible.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

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



> From: Radim Blazek <radim.blazek at gmail.com>
> Date: Tue, 5 Sep 2006 10:50:37 +0200
> To: Hamish <hamish_nospam at yahoo.com>
> Cc: Michael Barton <michael.barton at asu.edu>, <hmitaso at unity.ncsu.edu>,
> <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] v.in.ogr broken (\w shp)
> 
> On 9/5/06, Hamish <hamish_nospam at yahoo.com> wrote:
>> discussed this recently,
>>   http://thread.gmane.org/gmane.comp.gis.grass.devel/14634/
>> 
>> As William's points out there, all vector attributes are stored in one
>> file per mapset. This is problematic for:
>>  - backups or easy transfer of a single map to another system
>>  - disk error etc would trash all vectors in mapset, not just the one map
>>  - with many vector maps in the same mapset 32bit users will rapidly hit
>>    the 2gb file size limit.
>> 
>> Is per-map $MAPSET/vector/$MAPNAME/sqlite.db (or similar) possible?
> 
> Yes. This is discussed in my vector TODO, maybe you can look at
> http://freegis.org/cgi-bin/viewcvs.cgi/*checkout*/grass6/doc/vector/TODO?rev=1
> .2
> Chapter 1.2 Attributes.
> The problem with db per map is that you cannot do joins from tables in
> more maps and you cannot use db.* commands without database option.
> 
> Radim