On Nov 10, 2005, at 3:55 PM, Jed O. Kaplan wrote:
Kirk,
I had success by specifying the complete path to the DBF database in the from_database= argument instead of ./ as in the example in the man pages.
Jed,
That solved my troubles too.
I have noticed that GRASS seems to be very picky about using explicit paths to data directories (at least on a Mac). For example I often have problems if I use the short cut (~/) to refer to my home directory. I can't think of specific commands off the top of my head right now, but I was wondering if anyone could confirm this to be an issue on Linux machines as well?
Kirk
GRASS 6.1.cvs (engadin-swissgrid):~ > db.copy from_driver=dbf from_database='/Users/jkaplan/Documents/grass/engadin-swissgrid/PERMANENT/dbf/' from_table=mapcodes2 to_driver=pg to_database="host=localhost,dbname=engadin" to_table=mapcodes3
Seems to work!
Cheers,
Jed
On 10 Nov 2005, at 20:16, Kirk R. Wythers wrote:
On Nov 8, 2005, at 4:24 AM, Jed O. Kaplan wrote:
GRASS 6.1.cvs (engadin-swissgrid):~ > db.copy from_driver=dbf from_database=./ from_table=mapcodes2 to_driver=pg to_database="host=localhost,dbname=engadin" to_table=mapcodes2
DBMI-DBF driver error:
Table 'mapcodes2' doesn't exist.Did you try creating the table 'mapcodes' in postgres first before copying from dbf? Does anyone know if this is a required step?
Kirk
Error in db_open_select_cursor()