Changes in release 3.23.x (Recent; still supported)

Table of Contents

214. Changes in release 3.23.59 (not released yet)
215. Changes in release 3.23.58 (11 Sep 2003)
216. Changes in release 3.23.57 (06 Jun 2003)
217. Changes in release 3.23.56 (13 Mar 2003)
218. Changes in release 3.23.55 (23 Jan 2003)
219. Changes in release 3.23.54 (05 Dec 2002)
220. Changes in release 3.23.53 (09 Oct 2002)
221. Changes in release 3.23.52 (14 Aug 2002)
222. Changes in release 3.23.51 (31 May 2002)
223. Changes in release 3.23.50 (21 Apr 2002)
224. Changes in release 3.23.49
225. Changes in release 3.23.48 (07 Feb 2002)
226. Changes in release 3.23.47 (27 Dec 2001)
227. Changes in release 3.23.46 (29 Nov 2001)
228. Changes in release 3.23.45 (22 Nov 2001)
229. Changes in release 3.23.44 (31 Oct 2001)
230. Changes in release 3.23.43 (04 Oct 2001)
231. Changes in release 3.23.42 (08 Sep 2001)
232. Changes in release 3.23.41 (11 Aug 2001)
233. Changes in release 3.23.40
234. Changes in release 3.23.39 (12 Jun 2001)
235. Changes in release 3.23.38 (09 May 2001)
236. Changes in release 3.23.37 (17 Apr 2001)
237. Changes in release 3.23.36 (27 Mar 2001)
238. Changes in release 3.23.35 (15 Mar 2001)
239. Changes in release 3.23.34a
240. Changes in release 3.23.34 (10 Mar 2001)
241. Changes in release 3.23.33 (09 Feb 2001)
242. Changes in release 3.23.32 (22 Jan 2001: Production)
243. Changes in release 3.23.31 (17 Jan 2001)
244. Changes in release 3.23.30 (04 Jan 2001)
245. Changes in release 3.23.29 (16 Dec 2000)
246. Changes in release 3.23.28 (22 Nov 2000: Gamma)
247. Changes in release 3.23.27 (24 Oct 2000)
248. Changes in release 3.23.26 (18 Oct 2000)
249. Changes in release 3.23.25 (29 Sep 2000)
250. Changes in release 3.23.24 (08 Sep 2000)
251. Changes in release 3.23.23 (01 Sep 2000)
252. Changes in release 3.23.22 (31 Jul 2000)
253. Changes in release 3.23.21
254. Changes in release 3.23.20
255. Changes in release 3.23.19
256. Changes in release 3.23.18
257. Changes in release 3.23.17
258. Changes in release 3.23.16
259. Changes in release 3.23.15 (May 2000: Beta)
260. Changes in release 3.23.14
261. Changes in release 3.23.13
262. Changes in release 3.23.12 (07 Mar 2000)
263. Changes in release 3.23.11
264. Changes in release 3.23.10
265. Changes in release 3.23.9
266. Changes in release 3.23.8 (02 Jan 2000)
267. Changes in release 3.23.7 (10 Dec 1999)
268. Changes in release 3.23.6
269. Changes in release 3.23.5 (20 Oct 1999)
270. Changes in release 3.23.4 (28 Sep 1999)
271. Changes in release 3.23.3
272. Changes in release 3.23.2 (09 Aug 1999)
273. Changes in release 3.23.1
274. Changes in release 3.23.0 (05 Aug 1999: Alpha)

Please note that since release 4.0 is now production level, only critical fixes are done in the 3.23 release series. You are recommended to upgrade when possible, to take advantage of all speed and feature improvements in 4.0. See Upgrading-from-3.23.

The 3.23 release has several major features that are not present in previous versions. We have added three new table types:

MyISAM A new ISAM library which is tuned for SQL and supports large files.
InnoDB A transaction-safe storage engine that supports row level locking, and many Oracle-like features.
BerkeleyDB or BDB Uses the Berkeley DB library from Sleepycat Software to implement transaction-safe tables.

Note that only MyISAM is available in the standard binary distribution.

The 3.23 release also includes support for database replication between a master and many slaves, full-text indexing, and much more.

All new features are being developed in the 4.x version. Only bug fixes and minor enhancements to existing features will be added to 3.23.

The replication code and BerkeleyDB code is still not as tested and as the rest of the code, so we will probably need to do a couple of future releases of 3.23 with small fixes for this part of the code. As long as you don't use these features, you should be quite safe with MySQL 3.23!

Note that the above doesn't mean that replication or Berkeley DB don't work. We have done a lot of testing of all code, including replication and BDB without finding any problems. It only means that not as many users use this code as the rest of the code and because of this we are not yet 100% confident in this code.