[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:  new
  Priority:  blocker      |  Milestone:  7.0.5
 Component:  Database     |    Version:  unspecified
Resolution:               |   Keywords:  postgresql db.connect
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-----------------------------------

Comment (by martinl):

 Replying to [comment:26 mlennert]:
 > Example (after disabling the condition check mentioned above):
 >
 > {{{
 > createdb -h myRemoteServer testgrass2
 > db.connect driver=pg database=testgrass2
 > db.login host=myRemoteHost
 > db.tables -p
 > }}}
 >
 > Everything works, no tables shown. But then:

 OK, so it means that DB is empty, right?

 > {{{
 > D1/1: G_set_program_name(): v.in.ogr
 > D1/1: Using dsn=PG:dbname=testgrass2 host=myRemoteServer
 > ERREUR :Layer <boundary_county> not available
 > D1/1: G_set_program_name(): g.gisenv
 > }}}

 I do not understand - DB is empty, so why do you expect that `v.in.ogr`
 will not fail?

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