From: | Michael Swierczek <mike(dot)swierczek(at)gmail(dot)com> |
---|---|
To: | John Payne <jcpayne(at)uw(dot)edu> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: failure and silence of SQL commands |
Date: | 2011-04-28 18:04:43 |
Message-ID: | BANLkTi=qN4-RLeaTz=e3Hb-mXmQPkiLtbA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Thu, Apr 28, 2011 at 1:21 PM, John Payne <jcpayne(at)uw(dot)edu> wrote:
> Thank you both very much for your help; that was the problem. Stupid of me
> (the answer came to me in the shower this morning as well). If anyone out
> there in the developer community is listening, may I respectfully suggest
> that PSQL’s behavior --- to return nothing when Enter is hit – is
> pathological. It would be so simple to return a message like ”Waiting for
> the end of the statement…” and it would save novices like me a lot of very
> unhappy hours.
>
You're more ambitious than I was. When I started using PostgreSQL I
found psql intimidating so I used pgAdmin3 whenever possible.
pgAdmin3 is excellent and in my opinion much more friendly to us
novices than psql. Good luck.
Regards,
Mike
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-04-28 18:30:24 | Re: failure and silence of SQL commands |
Previous Message | Leif Biberg Kristensen | 2011-04-28 18:02:40 | Re: failure and silence of SQL commands |