Opened 9 years ago
Last modified 6 years ago
#2847 new enhancement
Allow users to define PG as their default DB backend globally
Reported by: | sbl | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.6.2 |
Component: | Database | Version: | unspecified |
Keywords: | db.connect, t.connect, PostgreSQL | Cc: | |
CPU: | Unspecified | Platform: | All |
Description
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...
Change History (9)
comment:1 by , 9 years ago
Type: | defect → enhancement |
---|
comment:2 by , 8 years ago
Milestone: | 7.1.0 → 7.2.0 |
---|
comment:4 by , 7 years ago
Milestone: | 7.2.1 → 7.2.2 |
---|
comment:5 by , 7 years ago
Milestone: | 7.2.2 → 7.4.0 |
---|
All enhancement tickets should be assigned to 7.4 milestone.
Milestone renamed