The official MySQL Lifecycle Policy calendar terminates the end of the Active Support Lifecycle for MySQL 4.1 at the end of this year. The product is then entering the Extended Support Lifecycle. Please click on the image and read "What is the difference between Active Lifecycle and Extended Lifecycle support?" to understand the implications of this.
(by Gerardo Narvaja)
We do run on all platforms supported by Microsoft, embedded platforms not tested. We do support all communication protocols supported by Windows. Minimum disk space: 200MB, basically enough to unpack, install and create a few test DBs. We do run on all filesystems supported by Windows, for tables larger than 4GB NTFS is necessary. We do support a lot of DB access frameworks: ODBC, .NET (1.1 or newer), JDBC (1.4.2 or larger to develop, 1.3.0 or newer to run).
Packages are named a bit differently than on Unix.
Continue reading "MySQL on Windows for DBAs"
As a service to the busy, here are
SuSE 10.0 RPMs of 5.0.19 a/o 2005-12-27 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.
As a service to the busy, here are
SuSE 9.3 RPMs of 5.0.13 a/o 2005-09-09 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.
As a service to the busy, here are
SuSE 9.3 RPMs of 5.0.12 a/o 2005-08-30 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.
As a service to the busy, here are
MySQL Query-browser 1.1.12 and
MySQL Administrator 1.0.22a RPMs (SuSE 9.3, MySQL 5).
These are builds from the MySQL download section, not the repository.
Update recommended especially for the Query-Browser; the UI was improved, and I no longer get a crash I used to get with the SuSE binary.
As a service to the busy, here are
SuSE 9.3 RPMs of 5.0.11 a/o 2005-07-28 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.
