manual.texi SHOW KEYS updated, NEWS updated (524ba9c3) · Commits · Software / OSDI20 Artifacts / mariadb

Docs/manual.texi

+116 −107

Original line number	Diff line number	Diff line
		@@ -19927,6 +19927,8 @@ are returned:
		This is updated by running @code{isamchk -a}.
		@item @code{Sub_part} @tab Number of indexed characters if the column is
		only partly indexed. @code{NULL} if the entire key is indexed.
		@item @code{Comment} @tab Various remarks.
		For now, it tells whether index is FULLTEXT or not.
		@end multitable

		@cindex displaying, table status
		@@ -33038,7 +33040,7 @@ simple rename should get your data back.
		@cindex changing, column order
		@cindex tables, changing column order
		@node Change column order, , ALTER TABLE problems, Problems
		@Section How To Change the Order of Columns in a Table
		@section How To Change the Order of Columns in a Table

		The whole point of SQL is to abstract the application from the data
		storage format. You should always specify the order in which you wish to
		@@ -39159,8 +39161,10 @@ though, so Version 3.23 is not released as a stable version yet.
		@appendixsubsec Changes in release 3.23.29
		@itemize @bullet
		@item
		@code{SHOW KEYS} now shows whether key is FULLTEXT or not.
		@item
		Added new script, mysql-multi.server.sh. Thanks to
		Tim Bunce <Tim.Bunce@ig.co.uk> for modifying mysql.server to
		Tim Bunce @email{Tim.Bunce@@ig.co.uk} for modifying mysql.server to
		easily handle hosts running many mysqlds.
		@item
		safe_mysqld, mysql.server and mysql_install_db have been modified
		@@ -39171,6 +39175,8 @@ made more consistent with how mysqld handles them by default.
		Automatically remove Berkeley DB transaction logs that are no longer in
		use.
		@item
		Fixed bug with several FULLTEXT indexes in one table.
		@item
		Added a warning if number of rows changes on @code{REPAIR}/@code{OPTIMIZE}.
		@item
		Applied patches for OS2 by @code{Yuri Dario}.
		@@ -39183,6 +39189,9 @@ that @code{mysql_install_db} core dumped on some Linux machines.
		@item
		Changed @code{mi_create()} to use less stack.
		@item
		Fixed bug with optimizer trying to over-optimize MATCH when used
		with UNIQUE key.
		@item
		Changed crash-me and the MySQL benchmarks to also work with FrontBase.
		@item
		Allow @code{RESTRICT} and @code{CASCADE} after @code{DROP TABLE} to make