MySQL Bugs: #1289: skip-innodb not documented

Bug #1289	skip-innodb not documented
Submitted:	15 Sep 2003 19:06	Modified:	16 Sep 2003 10:01
Reporter:	[ name withheld ]	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQLCC: Docs	Severity:	S3 (Non-critical)
Version:	3.23.51	OS:	n/a
Assigned to:		CPU Architecture:	Any

Description:
The MySQL Reference Manual does not document the skip-innodb 
configuration file and command line option.

There is one reference, in defining the have_innodb variable.
However, there is no definition or reference in text that
shows how to enable InnoDB support.

Additionally, Section 7.6, InnoDB Tables, doesn't have any 
reference to skip-innodb.  Specifically, nothing says that
using InnoDB table requires removing (or not specifying)
any skip-innodb option.

How to repeat:
 

Suggested fix:
The documentation of whichever executable (mysqld?) uses 
skip-innodb should define the option.

Something in section 7.6, InnoDB Tables, (probably 7.6.1) should 
say that using InnoDB table requires removing (or not specifying)
any skip-innodb option.

Thats clearly described: 
 
Chapter: 7.5 (http://www.mysql.com/doc/en/InnoDB_start.html) 
"If you don't want to use InnoDB tables, you can add the skip-innodb option to your MySQL 
option file. " 
 
Chapter 4.1.1 mysqld Command-line Options 
(http://www.mysql.com/doc/en/Command-line_options.html) 
"--skip-innodb  
Disable usage of Innodb tables. This will save memory and disk space and speed up some 
things. "

> Thats clearly described: 

You are reading the version number in bug reports, right?

Also, it would help if you mentioned the version number you're looking at.

(Your response implies that you think I missed the text you quoted, instead
of just that the current version no longer has the problem I reported 
against an older version.)

If the current version of the manual no longer has
the problem reported, then there is nothing to fix.

If you believe you've found a problem in the manual,
please check the current version to see if it still
exists in the current version. (For example, use
the online manual, which is always up to date.)
We don't make changes to manual versions that
are included with older releases.

> If the current version of the manual no longer has the problem reported, then 
> there is nothing to fix.

Of course.

> We don't make changes to manual versions that are included with older releases.

Of course too.  (I didn't mean that you should.)

http://www.mysql.com/doc/en/Command-line_options.html

at the current version points to Chapter 4.1.3 and doesn't contain any string like innodb.

http://www.mysql.com/doc/en/InnoDB_start.html

points at Chapter 14.2.4.and does indeed contain the startup option.

Since the Chapter about command line option has the usage of being a central reference point for the overview of command line options, it should contain a link to the detailed discussion of innodb and it's skipping.

Obviously, i am the second person stumbling over this matter.