[GRASS-user] grass 6.4.3 and db.connect

GRASS GRASS user
1

Hi,

I am using ‘db.connect’ to get access to a sqlite database. I have renamed the database extension from ‘.sqlite’ to ‘.db’ and placed it in the ‘PERMANENT’ directory but not entirely sure if i’ve correctly set this sqlite access up correctly. When i use ‘db.test’ i get the following error.

Unable to open database: unable to open database file

ERROR: Unable to open database <‘/home/username/dtm_location/PERMANENT/gisdata.db’>
ERROR: EXECUTE: ******** ERROR ********

I’m sure i’m probably making some simple errors in the configuration somewhere. Can anyone help with setup?

Many thanks,

–

Paul J. Shapley

2

Paul,

On Fri, Jan 31, 2014 at 10:43 PM, Paul Shapley <p.shapley@gmail.com> wrote:

Hi,

I am using 'db.connect' to get access to a sqlite database. I have renamed
the database extension from '.sqlite' to '.db' and placed it in the
'PERMANENT' directory but not entirely sure if i've correctly set this
sqlite access up correctly.

Did you do the connection setting as outlined in the manual?

http://grass.osgeo.org/grass64/manuals/db.connect.html
--> SQLite

What do you get with
db.connect -p
?

Markus

3

(please keep the discussion on the list)

On Sat, Feb 1, 2014 at 8:16 PM, Paul Shapley <p.shapley@gmail.com> wrote:

Thanks for the prompt reply. Here is the output to 'db.connect -p'

------------------------------------------------------------------------------------------------------

(Sat Feb 1 19:03:04 2014)
db.connect -p
driver:sqlite
database:'/home/username/dtm_location/PERMANENT/gisdata.db'

So, this corresponds to:
/home/username/dtm_location/PERMANENT/gisdata.db'

Fine. One idea below:

schema:User Data
group:
(Sat Feb 1 19:03:04 2014) Command finished (0 sec)

Should i see the a list of sqlite tables when i type 'd.vect' because i
currently cannot.

Ok, in the end the issue is that the vector-DB connection fails? That is defined
with v.db.connect...

http://grass.osgeo.org/grass64/manuals/v.db.connect.html

v.db.connect -p vectormap
will show to which DB it is connected. I suspect that this link is
outdated (set with the same command, see manual for examples).

Hope this helps
Markus