Hi, I used to use db.test (with test=test1) to test my sqlite database connection. In the most recent verson of GRASS 6.4.3 (rev 52380) it seems to be broken. I tried it on some of my own databases and a freshly downloaded sample dataset (small NC dataset, mapset=sqlite). I started it from the gui but it just get stucked in the process (no output after several minutes)...stopping it leaves the database in an incosistent state.
Thats why I tried just to simply copy a vector file (e.g streams) from PERMANENT to sqlite. Then I get the error message: Unable to open header file of vector <streams@sqlite> Unable to read head file.... Somehow working with sqlite doesn't work properly on my machine (Ubuntu 12.04) although I the command sqlite3 in the terminal works.... I also tried it with 6.5 SVN (rev. 52380) and a fresh NC dataset again: db.test just gives: Busy SQLITE db, already waiting for 10 seconds... What else do I need to test so that someone of you might know the problem of my basic database functions (creating tables eg. when tranforming from raster to vector etc.)? Can anyone reproduce this or is it just a behavior due to my own compilation (configured with sqlite3 support)? /Johannes _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
