[GRASS-dev] [GRASS GIS] #1358: WinGRASS 6.4.1: SQLite driver errors: `Unable to open database'
GRASS GIS
trac at osgeo.org
Thu Jul 25 03:52:20 PDT 2013
#1358: WinGRASS 6.4.1: SQLite driver errors: `Unable to open database'
-------------------------------------+--------------------------------------
Reporter: rvanderweide | Owner: grass-dev@…
Type: defect | Status: new
Priority: minor | Milestone: 6.4.4
Component: Database | Version: 6.4.1 RCs
Keywords: wingrass, SQLite driver | Platform: MSWindows 7
Cpu: x86-64 |
-------------------------------------+--------------------------------------
Comment(by mlennert):
Replying to [comment:10 mmetz]:
> Replying to [comment:9 hamish]:
> > unless someone has a bright idea for a minimally invasive fix, bumping
it down the road a little ...
>
> With GRASS default settings, i.e. the sqlite database in the default
folder, this does not happen. Changing priority to minor, but the ticket
could also be closed as invalid. Essentially, this is a sqlite bug with
sqlite calling fsync() on the directory of the sqlite database even if the
directory contains files not related to the sqlite database.
With the latest wingrass7 (July 18), after installation and download of
the NC data set, I get the following error:
{{{
g.copy vect=roadsmajor at PERMANENT,roads2
DBMI-SQLite driver error:
Unable to open database:
C:\grassdata\North_Carolina\user1\sqlite\sqlite.db
unable to open database file
no database is open
Copy vector <roadsmajor at PERMANENT> to current mapset as <roads2>
DBMI-SQLite driver error:
Unable to open database:
C:\grassdata\North_Carolina\user1\sqlite\sqlite.db
unable to open database file
WARNING: Impossible d'ouvrir la base de données
<C:\grassdata\North_Carolina\user1\sqlite\sqlite.db> avec le driver
<sqlite>
no database is open
WARNING: Impossible de copier la table <roads2>
WARNING: Unable to copy <roadsmajor at PERMANENT> to current mapset as
<roads2>
}}}
Is this related ?
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1358#comment:11>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list