Cookies op Tweakers

Tweakers maakt gebruik van cookies, onder andere om de website te analyseren, het gebruiksgemak te vergroten en advertenties te tonen. Door gebruik te maken van deze website, of door op 'Ga verder' te klikken, geef je toestemming voor het gebruik van cookies. Wil je meer informatie over cookies en hoe ze worden gebruikt, bekijk dan ons cookiebeleid.

Meer informatie

Software-update: MySQL 4.1.18

Het ontwikkelteam van MySQL heeft een nieuwe versie van de 4.1-tak uitgebracht. Het gaat om versie 4.1.18, die via deze pagina voor een groot aantal besturingssystemen gedownload kan worden. De oplettende MySQL-gebruiker heeft in de gaten dat versie 4.1.17 eigelijk uitgebracht zou moeten worden, maar door een showstopper die in versie 4.1.16 is gevonden werd besloten om 4.1.17 niet uit te brengen. Gebruikers die versie 4.1.15 of eerder op hun server draaien worden aangeraden om naar deze nieuwe versie te upgraden. Wat de veranderingen zijn van MySQL 4.1.18 lees je hieronder, waar ook de het changelog van 4.1.17 is te vinden:

Due to a critical performance related bug (Bug#15935) 4.1.17 was not released. The bug was introduced within 4.1.16, we therefore recommend all users to upgrade directly to 4.1.18 if they are using 4.1.15 or earlier.

Changes in release 4.1.18

    Functionality added or changed:
    • NDB Cluster: More descriptive warnings are now issued when inappropriate logging parameters are set in config.ini. (Formerly, the warning issued was simply Could not add logfile destination .) (Bug#11331 (
    • libmysqlclient now uses versioned symbols with GNU ld. (Bug#3074 (
    Bugs fixed:
    • The --replicate-do and --replicate-ignore options were not being enforced on multi-table statements. (Bug#15699 (, Bug#16487 (
    • Running out of diskspace in the location specified by the tmpdir option resulted in incorrect error message. (Bug#14634 (
    • Test suite func_math test returned warnings when server not compiled with InnoDB support. (Bug#15429 (
    • The MBROverlaps GIS function returned incorrect results. (Bug#14320 (
    • A CREATE TABLE ... SELECT ... on an equation involving DOUBLE values could result in the table being created with columns too small to hold the equation result. (Bug#9855 (
    • UPDATE statement crashed multi-byte character set FULLTEXT index if update value was almost identical to initial value only differing in some spaces being changed to " ";. (Bug#16489 (
    • Single table UPDATE statements without ORDER BY clauses which updated the same indexed column that was being filtered on were optimized with a full index scan instead of a more appropriate index range scan. (Bug#15935 (
    • A prepared statement created from a SELECT ... LIKE query (such as PREPARE stmt1 FROM 'SELECT col_1 FROM tedd_test WHERE col_1 LIKE ?';) would begin to produce erratic results after being executed repeatedly numerous (thousands) of times. (Bug#12734 (
Changes in 4.1.17 (Not released)
    Functionality added or changed:
    • In the latin5_turkish_ci collation, the order of the characters A WITH CIRCUMFLEX, I WITH CIRCUMLEX, and U WITH CIRCUMFLEX was changed. If you have used these characters in any indexed columns, you should rebuild those indexes. (Bug#13421 (
    • Support files for compiling with Visual Studio 6 have been removed. (Bug#15094 (
    • Internal sha1_result function renamed to mysql_sha1_result to prevent conflicts with other projects. (Bug#13944 (
    Bugs fixed:
    • Performing a RENAME TABLE on an InnoDB table when the server is started with the --innodb-file-per-table and the data directory is a symlink caused a server crash. (Bug#15991 (
    • The mysql_stmt_attr_get function returned an unsigned int instead of a boolean for STMT_ATTR_UPDATE_MAX_LENGTH. (Bug#16144 (
    • Characters in the gb2312 and euckr character sets which did not have Unicode mappings were truncated. (Bug#15377 (
    • Piping the fill_help_tables.sql file into mysqld resulted in a syntax error. (Bug#15965 (
    • NDBCluster: Upon the completion of a scan where a key request remained outstanding on the primary replica and a starting node died, the scan did not terminate. This caused incompleted error handling of the failed node. (Bug#15908 (
    • Using CAST() to convert values with long fractional and/or exponent parts to TIME returned wrong results. (Bug#12440 (
    • An INSERT ... SELECT statement between tables in a MERGE set can return errors when statement involves insert into child table from merge table or vice-versa. (Bug#5390 (
    • Certain permission management statements could create a NULL hostname for a user, resulting in a server crash. (Bug#15598 (
    • For InnoDB tables, using a column prefix for a utf8 column in a primary key caused Cannot find record errors when attempting to locate records. (Bug#14056 (
    • Certain CREATE TABLE ... AS ... statements involving ENUM columns could cause server crash. (Bug#12913 (
    • Using an aggregate function as the argument for a HAVING clause would result in the aggregate function always returning FALSE. (Bug#14274 (
    • The COALESCE() function truncated data in a TINYTEXT column. (Bug#15581 (
    • InnoDB: Comparison of indexed VARCHAR CHARACTER SET ucs2 COLLATE ucs2_bin columns using LIKE could fail. (Bug#14583 (
    • Issuing a DROP USER command could cause some users to encounter a hostname is not allowed to connect to this MySQL server error. (Bug#15775 (
    • Access Denied error could be erroneously returned with specific grant combinations under high load. (Bug#7209 (
    • Symbolic links did not function properly on Windows platforms. (Bug#14960 (, Bug#14310 (
    • BDB: A DELETE, INSERT, or UPDATE of a BDB table could cause the server to crash where the query contained a subquery using an index read. (Bug#15536 (
    • DELETE could report full-text index corruption (Invalid key for table ...) if the index was built with repair-by-sort, the data in the full-text index used UCA collation, and some word appeared in the data terminated by a 0xC2A0 character as well as by other non-letter characters. (Bug#11336 (
    • A race condition when creating temporary files caused a deadlock on Windows with threads in Opening tables or Waiting for table states. (Bug#12071 (
    • InnoDB: If FOREIGN_KEY_CHECKS was 0, InnoDB allowed inconsistent foreign keys to be created. (Bug#13778 (
    • NDB Cluster: A memory leak occurred when performing ordered index scans using indexes a columns larger than 32 bytes, which would eventually lead to the forced shutdown of all mysqld server processes used with the cluster. (Bug#13078 (
    • NDB Cluster: Under some circumstances, it was possible for a restarting node to undergo a forced shutdown. (Bug#15632 (
    • NDB Cluster: If an abort by the Transaction Coordinator timed out, the abort condition was incorrectly handled, causing the transacviton record to be released prematurely. (Bug#15685 (
    • NDB Cluster: A node which failed during cluster startup was sometimes not removed from the internal list of active nodes. (Bug#15587 (
    • NDB Cluster: There was a small window for a node failure to occur during a backup without an error being reported. (Bug#15425 (
    • Multiple-table update operations were counting updates and not updated rows. As a result, if a row had several updates it was counted several times for the "rows matched" value but updated only once. (Bug#15028 (
    • SELECT queries that began with an opening parenthesis were not being placed in the query cache. (Bug#14652 (
Versienummer 4.1.18
Besturingssystemen Windows 9x, Windows NT, Windows 2000, BSD, Windows XP, Linux x86, macOS, Solaris, UNIX, Windows Server 2003, Linux AMD64, Linux IA-64
Website MySQL
Licentietype Voorwaarden (GNU/BSD/etc.)

Door Robin Vreuls


08-02-2006 • 14:00

4 Linkedin Google+

Bron: MySQL


Meer historie

Reacties (4)

Wijzig sortering
Mmmm... ik ben wat huiverig geworden met MySQL upgrades.

Ik heb al meer dan eens corrupte databases gekregen bij het overzetten naar andere versies, terwijl ik toch alle im- en export acties met tools van MySQL zelf gedaan heb.

En nee, ik ben niet de enige op deze planeet die dat had!

Pas dus op en backup! En upgrade niet als het niet strikt noodzakelijk is!
"En upgrade niet als het niet strikt noodzakelijk is!"

Sorry maar dat vind ik echt een "minder slimme" opmerking. Upgraden naar nieuwere versies zijn niet voor niets; er zijn nieuwe features, het werkt sneller of er zijn bugs gefixed. De instelling 'blijven bij wat je hebt want het werkt toch?" slaat dus echt nergens op; mensen zoals jij worden volgens mij het eerste gehacked.. Heb zelf nog nooit problemen gehad met MySQL upgraden, maar goed... (en het spreekt voor zich dat je goede backups bijhoud, als je een goede systeembeheerder bent dan..)
Sorry, maar makaman heeft gewoon gelijk.
Upgrade niet, als het niet noodzakelijk is.

Mochten er bugs gefixed zijn waarvan je eerst last had, dan is het noodzakelijk.
Meteen naar een nieuwe versie overgaan is gewoon erg onverstandig.
Nu nog iets vinden tegen het misbruik van pagefile, vermits ik 277MB toch wel veel vindt voor zo'n relatief "klein" programma

Op dit item kan niet meer gereageerd worden.

Apple iPhone 11 Nintendo Switch Lite LG OLED C9 Google Pixel 4 FIFA 20 Samsung Galaxy S10 Sony PlayStation 5 Formule 1

'14 '15 '16 '17 2018

Tweakers vormt samen met Hardware Info, AutoTrack,, Nationale Vacaturebank, Intermediair en Independer DPG Online Services B.V.
Alle rechten voorbehouden © 1998 - 2019 Hosting door True