[GRASS-dev] [GRASS GIS] #2385: v.in.ogr doesn't use information from dblogin file about external PostgreSQL server

[GRASS GIS]

#2385: v.in.ogr doesn't use information from dblogin file about external
PostgreSQL server
-------------------------+-------------------------------------------------
  Reporter:  hemeybo     |      Owner:  grass-dev@…
      Type:  defect      |     Status:  new
  Priority:  normal      |  Milestone:  7.0.0
 Component:  Database    |    Version:  svn-releasebranch70
Resolution:              |   Keywords:  v.in.ogr PostgreSQL db.login
                         |  db.databases
       CPU:  x86-64      |   Platform:  Linux
-------------------------+-------------------------------------------------

Comment (by martinl):

 I have implemented experimental support for `db.login` settings to
 `v.in.ogr` and `v.external` in r67510. There is unfortunately a duplicated
 code (`dsn.c`) which would be probably good to move to Vlib to avoid code
 duplication. We will need similar code for `v.out.ogr`, `v.out.postgis`
 and `v.external.out`. These modules already contain a duplicated code
 (list layers). It would make sense to move this duplicated code to the
 library (a new one, eg. `libgrass_gdal`) or to Vlib.

 Similar situation for `r.in.gdal`, `r.external` and `r.external.out`. From
 this point of view a new library which would provide listing layers (both
 raster and vector), setting datasource would make more sense.

 What do you think? Better ideas?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2385#comment:5>
GRASS GIS <https://grass.osgeo.org>