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

Door , , 6 reacties
Bron: MySQL AB, submitter: Venga AB

MySQL AB heeft een nieuwe versie uitgegeven van MySQL 5.0, een populaire open-sourcedatabaseserver, en het versienummer opgekrikt naar 5.0.16. Het changelog zit zoals gewoonlijk bomvol met veranderingen en verbeteringen die er als volgt uitzien:

Functionality added or changed:
  • Added the Compression status variable, which indicates whether the client connection uses compression in the client/server protocol.
  • In MySQL 5.0.13, syntax for DEFINER and SQL SECURITY clauses was added to the CREATE VIEW and ALTER VIEW statements, but the clauses had no effect. They now are enabled. They specify the security context to be used when checking access privileges at view invocation time. See Section 19.2, “CREATE VIEW Syntax” for more information.
  • The InnoDB, NDB, BDB, and ARCHIVE storage engines now support spatial columns. See Chapter 16, Spatial Extensions in MySQL.
  • You must now declare a prefix for an index on any column of any Geometry class, the only exception being when the column is a POINT. (Bug #12267)
  • Added a --hexdump option to mysqlbinlog that displays a hex dump of the log in comments. This output can be helpful for replication debugging.
  • MySQL 5.0 now supports character set conversion for seven additional cp950 characters into the big5 character set: 0xF9D6, 0xF9D7, 0xF9D8, 0xF9D9, 0xF9DA, 0xF9DB, and 0xF9DC. Note: If you move data containing these additional characters to an older MySQL installation which does not support them, you may encounter errors. (Bug #12476)
Bugs fixed:
  • For some stored functions dumped by mysqldump --routines, the function definition could not be reloaded later due to a parsing error. (Bug #14723)
  • For a MyISAM table originally created in MySQL 4.1, INSERT DELAYED could cause a server crash. (Bug #13707)
  • The --exit-info=65536 option conflicted with --temp-pool and caused problems with the server's use of temporary files. Now --temp-pool is ignored if --exit-info=65536 is specified. (Bug #9551)
  • ORDER BY DESC within the GROUP_CONCAT() function was not honored when used in a view. (Bug #14466)
  • A comparison with an invalid date (such as WHERE col_name > '2005-09-31') caused any index on col_name not to be used and a string comparison for each row, resulting in slow performance. (Bug #14093)
  • Within stored routines, REPLACE() could return an empty string (rather than the original string) when no replacement was done, and IFNULL() could return garbage results. (Bug #13941)
  • Inserts of too-large DECIMAL values were handled inconsistently (sometimes set to the maximum DECIMAL value, sometimes set to 0). (Bug #13573)
  • Executing REPAIR TABLE, ANALYZE TABLE, or OPTIMIZE TABLE on a view for which an underlying table had been dropped caused a server crash. (Bug #14540)
  • A prepared statement that selected from a view processed using the merge algorithm could crash on the second execution. (Bug #14026)
  • Deletes from a CSV table could cause table corruption. (Bug #14672)
  • An update of a CSV table could cause a server crash. (Bug #13894)
  • For queries with nested outer joins, the optimizer could choose join orders that query execution could not handle. The fix is that now the optimizer avoids choosing such join orders. (Bug #13126)
  • Starting mysqld with the --skip-innodb and --default-storage-engine=innodb (or --default-table-type=innodb caused a server crash. (Bug #9815, re-fix of bug from 5.0.5)
  • mysqlmanager did not start up correctly on Windows 2003. (Bug #14537)
  • The parser did not correctly recognize wildcards in the host part of the DEFINER user in CREATE VIEW statements. (Bug #14256)
  • Memory corruption and a server crash could be caused by statements that used a cursor and generated a result set larger than max_heap_table_size. (Bug #14210)
  • mysqld_safe did not correctly start the -max version of the server (if it was present) if the --ledir option was given. (Bug #13774)
  • The mysql parser did not properly strip the delimiter from input lines less than nine characters long. For example, this could cause USE abc; to result in an Unknown database: abc; error. (Bug #14358)
  • Statements of the form CREATE TABLE … SELECT … that created a column with a multi-byte character set could incorrectly calculate the maximum length of the column, resulting in a Specified key was too long error. (Bug #14139)
  • Some updatable views could not be updated. (Bug #14027)
  • Running OPTIMIZE TABLE and other data-updating statements concurrently on an InnoDB table could cause a crash or the following warnings in the error log: Warning: Found locks from different threads in write: enter write_lock, Warning: Found locks from different threads in write: start of release lock. (Bug #11704)
  • Indexes for BDB tables were being limited incorrectly to 255 bytes. (Bug #14381)
  • Use of col_name = VALUES(col_name) in the ON DUPLICATE KEY UPDATE clause of an INSERT statement failed with an Column 'col_name' in field list is ambiguous error. (Bug #13392)
  • On Windows, the server was not ignoring hidden or system directories that Windows may have created in the data directory, and would treat them as available databases. (Bug #4375)
  • mysqldump could not dump views if the -x option was given. (Bug #12838)
  • mysqlimport now issues a SET @@character_set_database = binary statement before loading data so that a file containing mixed character sets (columns with different character sets) can be loaded properly. (Bug #12123)
  • Use of the deprecated --sql-bin-update-same option caused a server crash. (Bug #12974)
  • Maximum values were handled incorrectly for command-line options of type GET_LL. (Bug #12925)
  • For a user that has the SELECT privilege on a view, the server erroneously was also requiring the user to have the EXECUTE privilege at view execution time for stored functions used in the view definition. (Bug #9505)
  • Use of WITH ROLLUP PROCEDURE ANALYSE() could hang the server. (Bug #14138)
  • TIMEDIFF(), ADDTIME(), and STR_TO_DATE() were not reporting that they could return NULL, so functions that invoked them might misinterpret their results. (Bug #14009)
  • The example configuration files supplied with MySQL distributions listed the thread_cache_size variable as thread_cache. (Bug #13811)
  • Using ALTER TABLE to add an index could fail if the operation ran out of temporary file space. Now it automatically makes a second attempt that uses a slower method but no temporary file. In this case, problems that occurred during the first attempt can be displayed with SHOW WARNINGS. (Bug #12166)
  • The input polling loop for Instance Manager did not sleep properly. Instance Manager used up too much CPU as a result. (Bug #14388)
  • Trying to take the logarithm of a negative value is now handled in the same fashion as division by zero. That is, it produces a warning when ERROR_FOR_DIVISION_BY_ZERO is set, and an error in strict mode. (Bug #13820)
  • LOAD DATA INFILE would not accept the same character for both the ESCAPED BY and the ENCLOSED BY clauses. (Bug #11203)
  • The value of Last_query_cost was not updated for queries served from the query cache. (Bug #10303)
  • TIMESTAMPDIFF() returned an incorrect result if one argument but not the other was a leap year and a date was from March or later. (Bug #13534)
  • The server incorrectly accepted column definitions of the form DECIMAL(0,D) for D less than 11. (Bug #13667)
  • The displayed value for the CHARACTER_MAXIMUM_LENGTH column in the INFORMATION_SCHEMA.COLUMNS table was not adjusted for multi-byte character sets. (Bug #14290)
  • A bugfix in MySQL 5.0.15 caused the displayed values for the CHARACTER_MAXIMUM_LENGTH and CHARACTER_OCTET_LENGTH columns in the INFORMATION_SCHEMA.COLUMNS table to be reversed. (Bug #14207)
  • On Windows, the value of character_sets_dir in SHOW VARIABLES output was displayed inconsistenly (using both ‘/’ and ‘\’ as pathname component separators). (Bug #14137)
  • Subqueries in the FROM clause failed if the current database was INFORMATION_SCHEMA. (Bug #14089)
  • Corrected a parser precedence problem that resulted in an Unknown column … in 'on clause' error for some joins. (Bug #13832)
  • For LIKE … ESCAPE, an escape sequence longer than one character was accepted as valid. Now the sequence must be empty or one character long. If the NO_BACKSLASH_ESCAPES SQL mode is enabled, the sequence must be one character long. (Bug #12595)
  • SELECT DISTINCT CHAR(col_name) returned incorrect results after SET NAMES utf8. (Bug #13233)
  • A prepared statement failed with Illegal mix of collations if the client character set was utf8 and the statement used a table that had a character set of latin1. (Bug #12371)
  • Inserting a new row into an InnoDB table could cause DATETIME values already stored in the table to change. (Bug #13900)
  • The default value of query_prealloc_size was set to 8192, lower than its minimum of 16384. The minimum has been lowered to 8192. (Bug #13334)
  • The server did not take character set into account in checking the width of the mysql.user.Password column. As a result, it could incorrectly generate long password hashes even if the column was not long enough to hold them. (Bug #13064)
  • Inserting cp932 strings into a VARCHAR column caused a server crash rather than string truncation if the string was longer than the column definition. (Bug #12547)
  • Two threads that were creating triggers on an InnoDB table at the same time could deadlock. (Bug #12739)
  • mysqladmin and mysqldump would hang on SCO OpenServer. (Bug #13238)
  • RESET MASTER failed to delete log files on Windows. (Bug #13377)
  • Where one stored procedure called another stored procedure: If the second stored procedure generated an exception, the exception was not caught by the calling stored procedure. For example, if stored procedure A used an EXIT statement to handle an exception, subsequent statements in A would be executed regardless when A was called by another stored procedure B, even if an exception that should have been handled by the EXIT was generated in A. (Bug #7049)
  • Trying to create a stored routine with no database selected would crash the server. (Bug #13514, Bug #13587)
  • Specifying --default-character-set=cp-932 for mysqld would cause SQL scripts containing comments written using that character set to fail with a syntax error. (Bug #13487)
  • Trying to compile the server using the --without-geometry option caused the build to fail. (Bug #12991)
Versienummer:5.0.16
Besturingssystemen:Windows 9x, Windows NT, Windows 2000, Linux, BSD, Windows XP, Solaris, UNIX, Windows Server 2003
Website:MySQL AB
Download:http://dev.mysql.com/downloads/mysql/5.0.html
Licentietype:Voorwaarden (GNU/BSD/etc.)
Moderatie-faq Wijzig weergave

Reacties (6)

Ehm, 5.0 was toch al stable verklaard??? Zat er over te denken om over een maandje ofzo 5.0 te gaan installeren op ons intranet, maar als ik deze lijst met bug-fixes zie wacht ik nog wel even.
moet je je voorstellen, voor linux, windows en elk ander actief os komen elke maand nog zo'n 20 bugfixes uit! Jee, ik denk niet dat ik het ga instaleren ;)
Heb je wel gelezen wat de bug fixes zijn???

Server crashes om de meest simpele dingen
- Executing REPAIR TABLE, ANALYZE TABLE, or OPTIMIZE TABLE on a view for which an underlying table had been dropped caused a server crash. (Bug #14540)
- Starting mysqld with the --skip-innodb and --default-storage-engine=innodb (or --default-table-type=innodb caused a server crash. (Bug #9815, re-fix of bug from 5.0.5)
- Running OPTIMIZE TABLE and other data-updating statements concurrently on an InnoDB table could cause a crash or the following warnings in the error log: Warning: Found locks from different threads in write: enter write_lock, Warning: Found locks from different threads in write: start of release lock. (Bug #11704)
- Use of the deprecated --sql-bin-update-same option caused a server crash. (Bug #12974)

Nog steeds niet correct werkend
-order by met group_concat klopte niet in een view
- Inserts of too-large DECIMAL values were handled inconsistently (sometimes set to the maximum DECIMAL value, sometimes set to 0),For queries with nested outer joins, the optimizer could choose join orders that query execution could not handle. The fix is that now the optimizer avoids choosing such join orders. (Bug #13126)
- Inserting a new row into an InnoDB table could cause DATETIME values already stored in the table to change. (Bug #13900)

En mijn favoriet :
- Inserting cp932 strings into a VARCHAR column caused a server crash rather than string truncation if the string was longer than the column definition. (Bug #12547)
want server crash is de fout, dat we de string gewoon afkappen, waardoor output!=input, ipv een error geven is de gewenste functionaliteit. ;(

Nee, mij iets te veel server crashes bugfixes die ik zelf nog wel zie voorkomen om het echt in productie te gooien. Ik wacht denk ik wel op mysql voordat ik 5 in productie gooi.
Dus jij doet regelmatig een repair/analyze/optimize op een view waarvan je een onderliggende table hebt gedropt?

Get a grip.

En dat truncaten van strings, da's een setting. Je kunkunt ook gewoon een exception krijgen hoor.

Geen van de hier genoemde bugs zouden voor iemand showstoppers moeten zijn. En het beste nieuws: Ze zijn gefixt. Dus ze komen niet meer voor.

* 786562 cdwave
zoals met alle OpenSource software: your millage will vary :)

het is heel goed mogelijk dat in jouw specifieke situatie 5.x prima draait en nooit problemen zal geven. Het kan ook zijn dat 't ronduit bagger is. testen, testen en nog een testen.

Ik ga 't binnenkort eens op de testbank leggen voor wat serieuse mishandeling, als 't dat overleeft ga ik *misschien* overwegen om het in productie te nemen. :)
Ik heb zelf veel met Oracle gewerkt.. nah, daarmee is het met iedere versie kloten om het van scratch af aan op te bouwen! bug fixes horen bij een os/db. heb nog geen één oracle database gehad die ik niet hoefde te patchen bij aanvang/verloop van tijd.

Op dit item kan niet meer gereageerd worden.



Apple iOS 10 Google Pixel Apple iPhone 7 Sony PlayStation VR AMD Radeon RX 480 4GB Battlefield 1 Google Android Nougat Watch Dogs 2

© 1998 - 2016 de Persgroep Online Services B.V. Tweakers vormt samen met o.a. Autotrack en Carsom.nl de Persgroep Online Services B.V. Hosting door True