Re: Resolved: PostGreSQL - Accessing It

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Resolved: PostGreSQL - Accessing It
Date: 2003-08-16 15:40:19
Message-ID: 200308161540.h7GFeJt02895@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Karsten Hilbert wrote:
> > > test=# CREATE USER mel CREATEDB
> > > test-# \q
> > > bash-2.05b$ exit
> > > exit
> > > [mel(at)Cr168131-a mel]$ psql test
> > > psql: FATAL 1: user "mel" does not exist
> > >
> >
> > I just figured out my problem. As you can see from my CREATE USER
> > command above, I simply forgot to put the semicolon at the end. Doah!
> Does this not suggest that psql should print a warning:
> "still inside SQL query, really quit ? [y/n]" when in the
> above situation ?

That's an idea, but this is the first time someone has complained about
this. Seems we should see if more people are affected before adding a
"nag" option.

I wonder if we should have a "novice" mode for psql? Are there other
things it could control?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim Rosenberg 2003-08-16 15:56:14 Re: Resolved: PostGreSQL - Accessing It
Previous Message Jason Godden 2003-08-16 14:09:41 Re: summary and request