| From: | Neha Khatri <nehakhatri5(at)gmail(dot)com> |
|---|---|
| To: | Hubert Lubaczewski <depesz(at)depesz(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Why psql connection assumes default database name as the username |
| Date: | 2017-03-26 22:37:44 |
| Message-ID: | CAFO0U+_wMRkdFYUmwNBNe-=+u_bq4W6czttmQuaV=eF8kLzswg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Fri, Mar 24, 2017 at 7:57 PM, hubert depesz lubaczewski <
depesz(at)depesz(dot)com> wrote:
> On Fri, Mar 24, 2017 at 08:39:30AM +0000, Neha Khatri wrote:
> > Yes, so psql should say "Not sure which database to connect to. Please
> > specify a valid database name using -d option".
> > For backwards compatibility, psql can still attempt to connect to db with
> > name same as the username, but the error message could be more like
> > providing the information, what can be done next.
>
> Sorry, but I don't agree.
> I use databases named like users all the time, and love the fact that
> I don't have to provide dbname when it's obvious.
So, is it common practice to have a database name same as the username.
What are the usecase advantages of the database name and username mapping?
It would be good to understand.
Regards,
Neha
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2017-03-27 08:33:30 | Re: Why psql connection assumes default database name as the username |
| Previous Message | Andrew Zakharov | 2017-03-24 09:52:13 | Undo all changes made by production release |