MySQL-ism help patch for psql
in [PgSql]
|
Prev: Helping the CommitFest re PL/Perl changes
Next: [HACKERS] MonetDB test says that PostgreSQL often has errors or missing results
From: =?ISO-8859-1?Q?C=E9dric_Villemain?= on 25 Jan 2010 10:46 2010/1/25 Baron Schwartz <baron(a)xaprb.com>: > 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. Absolutly, that's why I suggest to give a simple option to activate those helpers. We didn't remove extra lines on the psql login to add anothers now. -- 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: "Alastair \"Bell\" Turner" on 25 Jan 2010 11:06 If this option is designed to help people's transition - basically to get to them before they've got to most of the manual - having to turn it on will be pointless. It needs to be active by default. A way to avoid it being a default option in psql may be setting an alias as part of package installation so power users couid turn it off by without having to add a switch to their command lines. It's not going to have anything to say to experienced psql users anyway so it would probably not bug anyone enough to turn it off. Regards Alastair On Mon, Jan 25, 2010 at 5:46 PM, Cédric Villemain <cedric.villemain.debian(a)gmail.com> wrote: > 2010/1/25 Baron Schwartz <baron(a)xaprb.com>: >> 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. > > Absolutly, that's why I suggest to give a simple option to activate > those helpers. > We didn't remove extra lines on the psql login to add anothers now. > > -- > 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 > -- 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: Aidan Van Dyk on 25 Jan 2010 11:12 * Alastair Bell Turner <thebellhead(a)gmail.com> [100125 11:07]: > If this option is designed to help people's transition - basically to > get to them before they've got to most of the manual - having to turn > it on will be pointless. It needs to be active by default. A way to > avoid it being a default option in psql may be setting an alias as > part of package installation so power users couid turn it off by > without having to add a switch to their command lines. It's not going > to have anything to say to experienced psql users anyway so it would > probably not bug anyone enough to turn it off. I'ld be more comfortable for a line in t the more standard help along the lines of: "For more information on PSQL commands when coming from other databases, see the documentation." And then we can have a full discussion in the docs, psql man page, wherever, where you can actually *describe* the differences between the commands, etc, instead of loosing the useful information because of trying to stuff things into a 1-line message about something that might not have been intended... And then you can have a section on MySQL, SQLite, DB2, Informix, Firebird, Oracle, etc... Basically a section for whoever has an itch. a. -- Aidan Van Dyk Create like a god, aidan(a)highrise.ca command like a king, http://www.highrise.ca/ work like a slave.
From: Andrew Dunstan on 25 Jan 2010 11:14 Alastair "Bell" Turner wrote: > If this option is designed to help people's transition - basically to > get to them before they've got to most of the manual - having to turn > it on will be pointless. It needs to be active by default. > My problem with this whole idea is that it seems to be very MySQL-specific. Why aren't we providing help for users migrating from Oracle, Sybase, Informix, Ingres, DB2, SQLServer and Firebird, to name but a few? And if we turn all those on by default, we'll have a pretty horrible banner when starting psql. cheers andrew -- 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: "Alastair \"Bell\" Turner" on 25 Jan 2010 11:22
On Mon, Jan 25, 2010 at 6:14 PM, Andrew Dunstan <andrew(a)dunslane.net> wrote: > > My problem with this whole idea is that it seems to be very MySQL-specific. > Why aren't we providing help for users migrating from Oracle, Sybase, > Informix, Ingres, DB2, SQLServer and Firebird, to name but a few? And if we > turn all those on by default, we'll have a pretty horrible banner when > starting psql. > > cheers > > andrew > The easy way around that would be a message along the lines of ' \migrate for information on how the commands from your previous environment translate to psql' It's a bit verbose but could be trimmed I'm sure. The \migrate mysql, \migrate db2, \migrate ingres ... could all do their own thing. Some of the command specific responses won't be extened too much either since DESCRIBE and SHOW apply in multiple places similarly enough that the one line reminder could be interchangable. -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |