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. Changing priority to minor, but the ticket could also be closed as invalid. the sqlite database in the default folder, this does not happen. Unless someone has a bright idea for a minimally invasive fix, bumping it down the road a little. This does however not solve the issues mentioned by Glynn but at least some other issues I found with recent sqlite versions. But this example is unusual and would not happen in a standard GRASS mapset.Īnyway, I have changed the default location of the sqlite db in trunk r52829 from $MAPSET/sqlite.db to $MAPSET/sqlite/sqlite.db, such that sqlite, just like the dbf driver, gets its own exclusive directory. This fails because the OGR dsn/layer is still open because GRASS still needs to read it. The OGR dsn/layer is opened first, then the sqlite db. Here, both the shapefile to be imported and the sqlite database were in the same folder.
"When SQLite creates a journal file on Unix, it opens theĭirectory that contains that file and calls fsync() on theĭirectory, in an effort to push the directory information to disk." In this particular example, the import failed because of this 'feature' of recent sqlite versions: TortoiseSVN and Windows Search are common culprits. WARNING: Cannot copy to current mapset as Īpparently, this can happen on Windows due to other programs scanning files in the background, which prevents them from being replaced. WARNING: Unable to open database by driver GRASS 6.4> g.copy vector to current mapset as (2) Problem copying attribute table (imported in DBF) to SQLite database): Unable to open database: unable to open database file Projection of input dataset and current location appear to match GRASS 6.4> v.in.ogr dsn=C:\Test\pse.shp layer=pse output=pseĭatum not recognised by GRASS and no parameters found GRASS 6.4> db.connect driver=sqlite database="c:\Test\sqlite.db" (1) Problem importing shapefile while connected to a SQLite database: Let me attach the command lines for both examples: i did NOT have the problems described below. I recall that an earlier version of GRASS 6.4 used SQLite as the default driver. For example, errors emerge when i wish to import a shapefile, OR copy an attribute table from a shapefile that was previously imported using the DBF driver. Connecting to an SQLite database works fine - when the database does not yet exist, it seems to create an empty database, but i can't seem to access it. By default, GRASS starts up connected to DBF. I keep on getting SQLite driver errors when trying to use a newly created SQLite database ('unable to open database').
0 kommentar(er)
