[GRASS5] db.connect and auto-creation of dbf/ directory

[Markus Neteler]

On Thu, Apr 21, 2005 at 02:33:25PM -0700, Michael Barton wrote:
> I'd vote for g.copy. You need to have the dbf directory in existence for
> some modules to put something into. That is, you need it before there is
> anything IN it to connect with.

Excuse me, I don't understand your vote. You vote for leaving
this as-is? In the direction of Radim's comment?

Markus

> > From: Markus Neteler <neteler at itc.it>
> > Date: Thu, 21 Apr 2005 15:27:20 +0200
> > To: grass5 developers list <grass5 at grass.itc.it>
> > Subject: [GRASS5] db.connect and auto-creation of dbf/ directory
> > 
> > Hi,
> > 
> > when using db.connect to define in a new mapset the DB connection,
> > I face following non-feature:
> > 
> > db.connect driver=dbf database='$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/'
> > db.connect -p
> > driver:dbf
> > database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
> > schema:(null)
> > group:(null)
> > 
> > So far so nice. But:
> > 
> > g.copy vect=ammprv,pat_ammprv
> > COPY [ammprv at PERMANENT] to current mapset as [pat_ammprv]
> > DBMI-DBF driver error:
> > Cannot open dbf database: /ssi0/ssi/neteler/grassdata/pat/export/dbf/
> > 
> > WARNING: Cannot open database '/ssi0/ssi/neteler/grassdata/pat/export/dbf/'
> > no database is open
> > WARNING: Cannot copy table
> > WARNING: Cannot copy ammprv at PERMANENT to current mapset as pat_ammprv
> > 
> > Yes, I know, that the user has to create this directory first. But
> > this could also be done by the program.
> > 
> > So, where to apply a code modification:
> > - db.connect - when using dbf driver?
> > - g.copy/g.rename - when using dbf driver ?
> > 
> > Markus
> > 
> 

-- 
Markus Neteler     <neteler itc it>       http://mpa.itc.it
ITC-irst -  Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18        -       38050 Povo (Trento), Italy