Postgres Pro
Downloads
Home   >   mailing lists

Re: [GENERAL] Feature proposal, DBURL: psql pgsql://joe:p4zzw0rd@example.org:2345/dbname - Mailing list pgsql-general

From Hans Schou
Subject Re: [GENERAL] Feature proposal, DBURL: psql pgsql://joe:p4zzw0rd@example.org:2345/dbname
Date
Msg-id CAApBw35=jtTcAUD2tizwcOE0yrbHOGJthAatC51g6Tat5Nm=eA@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] Feature proposal, DBURL: psqlpgsql://joe:p4zzw0rd@example.org:2345/dbname  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: [GENERAL] Feature proposal, DBURL: psqlpgsql://joe:p4zzw0rd@example.org:2345/dbname  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Tree view
2017-07-05 15:41 GMT+02:00 Adrian Klaver <adrian.klaver@aklaver.com>:

[scheme[<+>dsn]]://[[username[:[password]]@][host][:port][/[dbname][/[[table[/[column[,column...]*]]]|sql]]]
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The thing is that in a quick search on this I did not find a reference implementation of this to compare against.

"dsn" is only relevant when the scheme is ODBC.

In a situation where an application (like Drupal) get connect string (URI) it should be able to find the right driver to use. In case with of ODBC, a dsn (Data Source Name) is needed.

./hans

pgsql-general by date:

Previous
From: Moreno Andreo
Date:
Subject: Re: [SPAM] Re: [GENERAL] Invalid field size
Next
From: Jeff Janes
Date:
Subject: Re: [GENERAL] Strange case of database bloat