MySQL Manual
7 MySQL Table Types
- 7.5
InnoDBTables- 7.5.15 InnoDB Change History
- 7.5.15.1 MySQL/InnoDB-4.0.14, July 22, 2003
- 7.5.15.2 MySQL/InnoDB-3.23.57, June 20, 2003
- 7.5.15.3 MySQL/InnoDB-4.0.13, May 20, 2003
- 7.5.15.4 MySQL/InnoDB-4.1.0, April 3, 2003
- 7.5.15.5 MySQL/InnoDB-3.23.56, March 17, 2003
- 7.5.15.6 MySQL/InnoDB-4.0.12, March 18, 2003
- 7.5.15.7 MySQL/InnoDB-4.0.11, February 25, 2003
- 7.5.15.8 MySQL/InnoDB-4.0.10, February 4, 2003
- 7.5.15.9 MySQL/InnoDB-3.23.55, January 24, 2003
- 7.5.15.10 MySQL/InnoDB-4.0.9, January 14, 2003
- 7.5.15.11 MySQL/InnoDB-4.0.8, January 7, 2003
- 7.5.15.12 MySQL/InnoDB-4.0.7, December 26, 2002
- 7.5.15.13 MySQL/InnoDB-4.0.6, December 19, 2002
- 7.5.15.14 MySQL/InnoDB-3.23.54, December 12, 2002
- 7.5.15.15 MySQL/InnoDB-4.0.5, November 18, 2002
- 7.5.15.16 MySQL/InnoDB-3.23.53, October 9, 2002
- 7.5.15.17 MySQL/InnoDB-4.0.4, October 2, 2002
- 7.5.15.18 MySQL/InnoDB-4.0.3, August 28, 2002
- 7.5.15.19 MySQL/InnoDB-3.23.52, August 16, 2002
- 7.5.15.20 MySQL/InnoDB-4.0.2, July 10, 2002
- 7.5.15.21 MySQL/InnoDB-3.23.51, June 12, 2002
- 7.5.15.22 MySQL/InnoDB-3.23.50, April 23, 2002
- 7.5.15.23 MySQL/InnoDB-3.23.49, February 17, 2002
- 7.5.15.24 MySQL/InnoDB-3.23.48, February 9, 2002
- 7.5.15.25 MySQL/InnoDB-3.23.47, December 28, 2001
- 7.5.15.26 MySQL/InnoDB-4.0.1, December 23, 2001
- 7.5.15.27 MySQL/InnoDB-3.23.46, November 30, 2001
- 7.5.15.28 MySQL/InnoDB-3.23.45, November 23, 2001
- 7.5.15.29 MySQL/InnoDB-3.23.44, November 2, 2001
- 7.5.15.30 MySQL/InnoDB-3.23.43, October 4, 2001
- 7.5.15.31 MySQL/InnoDB-3.23.42, September 9, 2001
- 7.5.15.32 MySQL/InnoDB-3.23.41, August 13, 2001
- 7.5.15.33 MySQL/InnoDB-3.23.40, July 16, 2001
- 7.5.15.34 MySQL/InnoDB-3.23.39, June 13, 2001
- 7.5.15.35 MySQL/InnoDB-3.23.38, May 12, 2001
7.5.15.6 MySQL/InnoDB-4.0.12, March 18, 2003
- In crash recovery InnoDB now prints the progress in percents of a transaction rollback.
- Fixed a bug/feature: if your application program used mysql_use_result(), and used >= 2 connections to send SQL queries, it could deadlock on the adaptive hash S-latch in btr0sea.c. Now mysqld releases the S-latch whenever it passes data from a SELECT to the client.
- Fixed a bug: MySQL could erroneously return 'Empty set' if InnoDB estimated an index range size to 0 records though the range was not empty; MySQL also failed to do the next-key locking in the case of an empty index range.
