[GRASS-dev] [GRASS GIS] #3985: Read-only operations shouldn't unnecessarily do null edits to sqlite database

[GRASS GIS]

#3985: Read-only operations shouldn't unnecessarily do null edits to sqlite
database
-------------------------+-------------------------
 Reporter:  jidanni      |      Owner:  grass-dev@…
     Type:  enhancement  |     Status:  new
 Priority:  trivial      |  Milestone:
Component:  Database     |    Version:  unspecified
 Keywords:               |        CPU:  Unspecified
 Platform:  Unspecified  |
-------------------------+-------------------------
 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
 }}}

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3985>
GRASS GIS <https://grass.osgeo.org>