Re: [GENERAL] Resolved: PostGreSQL - Accessing It
--On Saturday, August 16, 2003 11:40 AM -0400 Bruce Momjian <[EMAIL PROTECTED]> wrote: I wonder if we should have a "novice" mode for psql? Are there other things it could control? Change the prompt when output is redirected with \o. I don't know how many times I've redirected output with \o to get a single query in HTML, then forgotten that I did that and been puzzled why my subsequent queries didn't show any results! There's always this head-slap-the-forehead moment when I finally take a look at the HTML, and see all this "other" stuff on the end ... :-) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Resolved: PostGreSQL - Accessing It
Karsten Hilbert wrote: > > > test=# CREATE USER mel CREATEDB > > > test-# \q > > > bash-2.05b$ exit > > > exit > > > [EMAIL PROTECTED] 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 [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [GENERAL] Resolved: PostGreSQL - Accessing It
> > test=# CREATE USER mel CREATEDB > > test-# \q > > bash-2.05b$ exit > > exit > > [EMAIL PROTECTED] 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 ? Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[GENERAL] Resolved: PostGreSQL - Accessing It
> test=# CREATE USER mel CREATEDB > test-# \q > bash-2.05b$ exit > exit > [EMAIL PROTECTED] 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! I guess it's been a little while since I've done much SQL. I've since successfully made myself a user and life is good. Thanks for everyone's help. -- Mel Roman [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
