| From: | Alexander Shulgin <ash(at)commandprompt(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Notes on implementing URI syntax for libpq |
| Date: | 2011-11-29 20:02:37 |
| Message-ID: | 1322596520-sup-884@moon |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Alexander Shulgin's message of Sat Nov 26 22:07:21 +0200 2011:
>
> So how about this:
>
> postgresql:ssl://user:pw(at)host:port/dbname?sslmode=...
>
> The "postgresql:ssl://" designator would assume "sslmode=require", if not overriden in extra parameters and "postgresql://" would imply "sslmode=prefer". And to disable SSL you would pick either designator and append "sslmode=disable".
>
> The JDBC's "ssl=true" will translate to "sslmode=require".
Hey, I'm going to assume "no objections" equals "positive feedback" and continue hacking in this direction.
> If we can decide on this, we should also put reasonable effort into making JDBC support the same syntax.
What would be our plan on this? Since the syntax proposed here is strictly a superset of the existing JDBC syntax, I would think this qualifies as an improvement and it would be backwards compatible with any previous version of the JDBC connector.
--
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-11-29 20:09:59 | Re: Re: [patch] Include detailed information about a row failing a CHECK constraint into the error message |
| Previous Message | Alexander Shulgin | 2011-11-29 19:53:44 | Re: Notes on implementing URI syntax for libpq |