Opened 3 months ago

Last modified 2 months ago

#3985 new enhancement

Read-only operations shouldn't unnecessarily do null edits to sqlite database

Reported by: jidanni Owned by: grass-dev@…
Priority: trivial Milestone: 7.8.3
Component: Database Version: unspecified
Keywords: read-only grass.py Cc:
CPU: Unspecified Platform: Unspecified

Description

Even readonly commands,

$ grass /home/jidanni/grassdata/ruanbikeng/TC46 --exec g.gisenv
Starting GRASS GIS...
Cleaning up temporary files...
Executing <g.gisenv> ...
GISDBASE=/home/jidanni/grassdata
LOCATION_NAME=ruanbikeng
MAPSET=TC46
GUI=wxpython
Execution of <g.gisenv> finished.
Cleaning up default sqlite database ...
Cleaning up temporary files...
cause all this writing
$ find grassdata/ -mmin -1
grassdata/ruanbikeng/TC46
grassdata/ruanbikeng/TC46/sqlite
grassdata/ruanbikeng/TC46/sqlite/sqlite.db

even e.g.,

$ grass /home/jidanni/grassdata/ruanbikeng/TC46 --exec true

Change History (2)

comment:1 Changed 3 months ago by wenzeslaus

Keywords: read-only grass.py added

comment:2 Changed 2 months ago by neteler

Milestone: 7.8.3
Note: See TracTickets for help on using tickets.