[GRASS-dev] [GRASS GIS] #3167: db.connect: connection to remote database does not work

[GRASS GIS]

#3167: db.connect: connection to remote database does not work
--------------------------+-----------------------------------
  Reporter:  mlennert     |      Owner:  grass-dev@…
      Type:  defect       |     Status:  closed
  Priority:  blocker      |  Milestone:  7.0.5
 Component:  Database     |    Version:  unspecified
Resolution:  fixed        |   Keywords:  postgresql db.connect
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-----------------------------------
Changes (by mlennert):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Replying to [comment:28 martinl]:
 >
 > {{{
 > v.in.ogr in=PG:dbname=grassremote layer=ruian.staty out=staty --o
 > }}}
 >
 > in GRASS 70 it fails with
 >
 > {{{
 > ERROR 1: PQconnectdb failed.
 > FATAL:  database "grassremote" does not exist
 >
 > ERROR: Unable to open data source <PG:dbname=grassremote>
 > }}}
 >
 > See r67510, hard to backport. In GRASS70 you can still do
 >
 > {{{
 > v.in.ogr in="PG:dbname=grassremote host=myserver" layer=ruian.staty
 out=staty --o
 > }}}
 >
 > which works.

 Yes, and as I said before, I agree that trying to solve this issue is too
 heavy the day before a release. So, let's just call this a 'known issue'
 and tell people that they can use the complete dsn string in a v.in.ogr
 command line as a work-around.

 This is especially annoying for those that depend on the GUI wizards for
 import, but let's hope that it will be one more motivating element to
 switch to 7.2 as soon as it comes out (although I haven't tested 7.2 with
 the GUI wizard, yet).

 So, I'm closing this as fixed as the original issue is solved, and we'll
 just have to accept that 7.0 treatment of databases is imperfect.

 Thanks for going through all this with me !

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