On Thu, May 18, 2017 at 12:59 PM, Markus Neteler <nete...@osgeo.org> wrote: > > On Wed, May 17, 2017 at 3:03 PM, Markus Metz > <markus.metz.gisw...@gmail.com> wrote: > > On Wed, May 17, 2017 at 9:31 AM, Moritz Lennert > ... > >> I would, therefore, expect to just be able to do this: > >> > >> v.in.ogr "PG:host=myhost user=theuser password=thepassword > >> dbname=thedatabase" layer=theschema.thetable out=mygrassmap > > > > I agree > > Just a side-note: I would be very happy to not store the password in > the cmd line history. > PG itself supports a password file > (https://www.postgresql.org/docs/9.6/static/libpq-pgpass.html). > > Please keep any password hiding option(s) in mind when working on the design.
Apparently such a password file is recognized by the PostgreSQL client library, therefore no special mechanism should be needed for OGR or GRASS, but a hint in the manuals of db.login and v.in.ogr might be helpful. Markus M
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
