[GRASS-dev] [GRASS GIS] #3167: db.connect: connection to remote database does not work
GRASS GIS
trac at osgeo.org
Mon Sep 26 23:01:39 PDT 2016
#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 mlennert):
Replying to [comment:4 mlennert]:
> Replying to [comment:2 martinl]:
> > Replying to [ticket:3167 mlennert]:
> > > {{{
> > > createdb -h myRemoteServer testgrass
> > > grass70 -c /data/GRASS/DATA7/nc_spm_08/postgres_test
> > > db.connect driver=pg database="host=myRemoteServer,dbname=testgrass"
> > > }}}
> >
> > did you tried
> >
> > {{{
> > db.connect driver=pg database=testgrass
> > db.login driver=pg database=testgrass host=myRemoteServer
> > }}}
> >
>
I just noticed that the first sentence with the most important information
is missing:
Yes, I tried, but it didn't make a difference. Exact same error as before
and DEBUG=3 gives me:
D3/3: db_driver_open_database(): host = (null), port = (null), options =
(null), tty = (null), dbname = testgrass, user = (null), password = (null)
schema = (null)
> And if this is how it is supposed to be done, then we need to change the
man page.
>
> It just seems a bit redundant to have to indicate driver and database
twice...
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3167#comment:7>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list