[GRASS-dev] [GRASS GIS] #2847: Allow users to define PG as their default DB backend globally

GRASS GIS trac at osgeo.org
Mon Jan 4 05:22:29 PST 2016


#2847: Allow users to define PG as their default DB backend globally
---------------------------------------------+-------------------------
 Reporter:  sbl                              |      Owner:  grass-dev@…
     Type:  defect                           |     Status:  new
 Priority:  normal                           |  Milestone:  7.1.0
Component:  Database                         |    Version:  unspecified
 Keywords:  db.connect,t.connect,PostgreSQL  |        CPU:  Unspecified
 Platform:  All                              |
---------------------------------------------+-------------------------
 There is currently no way to for user(s) to define PostgreSQL as their the
 default DB backend (instead of SQLite). Other connection parameters than
 the default have to be defined for each mapset using ''db.connect''.
 Connection parameters are then stored in the mapset`s VAR file.

 A global setting in e.g. a file $HOME/.grass7/dbconnect_default which may
 contain e.g.:

 {{{
 driver=pg
 database=MY_DATABASE
 schema="$LOCATION_$MAPSET"
 group=MY_GROUP_USER
 }}}

 would be nice.

 But that would probably also require changes to the initialization of the
 DB backend, if the default behavior (meaning SQLite) should be overwritten
 (and would require that users are granted CREATE rights on SCHEMAs if one
 wants to have a schema per location/mapset combination)...

 Would be nice if such a setting could also be taken into account by
 t.connect...

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



More information about the grass-dev mailing list