From: Tom Lane on
David Christensen <david(a)endpoint.com> writes:
> Should the error messages between the SHOW cases and the others be
> consistent ("ERROR: unsupported command" or similar)? It's worth
> noting that this is only in the psql client, but we could simulate the
> ereport output from the server.

No. Not unless you want to simulate it to the point of honoring the
different verbosity settings, which would greatly expand the size of the
patch. We do not try to make the response to "help" look like an error
message, and I don't see the value of doing so here either.

(I think Florian's real problem with the proposed output is that it's
ugly, which I agree with --- the formatting is strange.)

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: David Christensen on

On Jan 21, 2010, at 12:02 PM, Tom Lane wrote:

> David Christensen <david(a)endpoint.com> writes:
>> Should the error messages between the SHOW cases and the others be
>> consistent ("ERROR: unsupported command" or similar)? It's worth
>> noting that this is only in the psql client, but we could simulate
>> the
>> ereport output from the server.
>
> No. Not unless you want to simulate it to the point of honoring the
> different verbosity settings, which would greatly expand the size of
> the
> patch. We do not try to make the response to "help" look like an
> error
> message, and I don't see the value of doing so here either.
>
> (I think Florian's real problem with the proposed output is that it's
> ugly, which I agree with --- the formatting is strange.)


I'm with you on that one; I tried to address that in the second
revision of the patch. But I'm definitely open to suggestions.

Regards,

David
--
David Christensen
End Point Corporation
david(a)endpoint.com





--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Baron Schwartz on
David Fetter just pointed this thread out to me. I think anything
that makes PostgreSQL more accessible could be a good thing. In some
sense it's harder to learn a technology when you are very familiar
with another similar one already. Is it easier to learn to type on
Dvorak, or to learn QWERTY and then switch to Dvorak? Switching was
harder for me than learning initially.

So I guess my advice, since David asked me :-) is not to underestimate
the pain of switching. I don't know whether this patch is the Right
Answer, but I think the sentiment is something to be encouraged. If
it's not the right answer, then maybe some brainstorming and user
input will reveal creative alternatives. I'll start:

== begin ==

Welcome to the POSTGRESQL interactive sql monitor:
Please read the file COPYRIGHT for copyright terms of POSTGRESQL

type \? for help on slash commands
type \mysql for a quick MySQL-to-PostgreSQL cheatsheet

somedb=> \mysql

psql uses backslash keywords instead of SHOW commands. There is
also a standard INFORMATION_SCHEMA if you're familiar with that.
The following commands might be helpful as you learn how to use psql:

Command in mysql Command in psql
================ ===============
SHOW TABLES \dt
DESCRIBE \d
... and so on.

== end ==

The full list of SHOW commands, should anyone be interested, is at
http://dev.mysql.com/doc/en/show.html

Cheers,
Baron

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: =?ISO-8859-1?Q?C=E9dric_Villemain?= on
2010/1/24 Baron Schwartz <baron(a)xaprb.com>:
> David Fetter just pointed this thread out to me.  I think anything
> that makes PostgreSQL more accessible could be a good thing.  In some
> sense it's harder to learn a technology when you are very familiar
> with another similar one already.  Is it easier to learn to type on
> Dvorak, or to learn QWERTY and then switch to Dvorak?  Switching was
> harder for me than learning initially.
>
> So I guess my advice, since David asked me :-) is not to underestimate
> the pain of switching.  I don't know whether this patch is the Right
> Answer, but I think the sentiment is something to be encouraged.  If
> it's not the right answer, then maybe some brainstorming and user
> input will reveal creative alternatives.  I'll start:

'psql --help mysql' (or 'psql --tips mysql' ) might be good to call a
special helper : I don't see the point to introduce that kind of
things when it is useless for most of our users. (so 'psql' won't
output any tips relative to mysql)

It offer then to have a 'psql --help oracle' or anyother special tips
we want to provide for our new users and following their knowledge.

And it will be able to provide usefull tips à la git for postgresql
regular users. (selcet --> did you mean select instead of selcet ?)


Regards,
Cédric

>
> == begin ==
>
> Welcome to the POSTGRESQL interactive sql monitor:
>  Please read the file COPYRIGHT for copyright terms of POSTGRESQL
>
>   type \? for help on slash commands
>   type \mysql for a quick MySQL-to-PostgreSQL cheatsheet
>
> somedb=> \mysql
>
> psql uses backslash keywords instead of SHOW commands.  There is
> also a standard INFORMATION_SCHEMA if you're familiar with that.
> The following commands might be helpful as you learn how to use psql:
>
>  Command in mysql  Command in psql
>  ================  ===============
>  SHOW TABLES       \dt
>  DESCRIBE          \d
>  ... and so on.
>
> == end ==
>
> The full list of SHOW commands, should anyone be interested, is at
> http://dev.mysql.com/doc/en/show.html
>
> Cheers,
> Baron
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>



--
Cédric Villemain

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Baron Schwartz on
Hi Cédric,

On Sun, Jan 24, 2010 at 5:11 PM, Cédric Villemain
<cedric.villemain.debian(a)gmail.com> wrote:
> 'psql --help mysql' (or 'psql --tips mysql' ) might be good to call a
> special helper : I don't see the point to introduce that kind of
> things when it is useless for most of our users.

I think it's good to go beyond what's useful for most users. It's
good to help potential users, too.

- Baron

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers