Your message dated Sat, 12 May 2012 20:56:36 +0100
with message-id <[email protected]>
and subject line not any discernible issue
has caused the Debian Bug report #427101,
regarding mysql help: last on line
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
427101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427101
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-client-5.0
Version: 5.0.38-3
Severity: wishlist
File: /usr/bin/mysql
mysql> ?
List of all MySQL commands:
Note that all text commands must be first on line and end with ';'
? (\?) Synonym for `help'.
clear (\c) Clear command.
connect (\r) Reconnect to the server. Optional arguments are db and host.
delimiter (\d) Set statement delimiter. NOTE: Takes the rest of the line as new
delimiter.
edit (\e) Edit command with $EDITOR.
ego (\G) Send command to mysql server, display result vertically.
"First on line"? You mean "last on a line"!
Also some don't work, e.g.,
SELECT * FROM wiki_site_stats ego;
is just like with no ego. Must use \G, and ego needs a ";" which \G
doesn't but no mention is made.
Should give examples.
P.S., the LIMIT SQL documentation does not say how to get e.g., the
last 10 rows of the output,
* The `LIMIT' clause can be used to constrain the number of rows
returned by the `SELECT' statement. `LIMIT' takes one or two
numeric arguments, which must be integer constants...
without doing extra calculations.
Hmmm, file:///usr/share/doc/postgresql-doc-8.2/html/queries-limit.html
tells me it is not that simple. OK, never mind.
--- End Message ---
--- Begin Message ---
Due to copyright constraints you don't get the full documentation. We
can look at documentation that is available and how it can be improved,
but it is limited.
The documentation inside the mysql client IS limited. But this complaint
is even less clear.
Also I don't see what postgres documentation (which is a different
dialect of SQL) has to do with it.
--- End Message ---
