mirror of
https://github.com/MariaDB/server.git
synced 2026-01-06 05:22:24 +03:00
418fcdf16a
as the already-stored timestamp. Now 'created' is used only to know if this is a first binlog or not. And we may re-use the superfluous bytes in 5.0 when we need room. sql/log_event.cc: This sort of reverts a change I made in 3.23.57. In 3.23.57 I set 'created' to 0 if this was a non-first binlog, so I made mysqlbinlog not print the "created xx" part if created == 0. While this was sensible, as 'created' is 0 or equal to the timestamp which is already stored in the event, we can always print "created xx" by using the timestamp, and leaving the use of 'created' only to know if this is a first binlog or not (which we print as "created at startup"). sql/log_event.h: In Start_log_event, 'created' is always the same as 'when', or O. We didn't need 4 bytes for this, a bit would have been enough (O or "same as 'when'"). Possibly in 5.0 we will re-use the useless bytes.
This is a release of MySQL, a GPL (free) SQL database server (more licence information in the PUBLIC file and in the reference manual). Please read the Upgrading section in the manual if emigration from 3.20.# to 3.21.#. Otherwise it wont work!! The latest information about MySQL can be found at: http://www.mysql.com To see what it can do take a look at the features section in the manual. For installation instructions see the Installation chapter in the manual. For future plans see the TODO appendix in the manual. New features/bug fixes history is in the news appendix in the manual. For the currently known bugs/misfeatures (known errors) see the bugs appendix in the manual. For examples of SQL and benchmarking information see the bench directory. The manual mentioned above can be found in the Docs directory. The manual is available in the following formats: as text in Docs/manual.txt, as HTML in Docs/manual_toc.html, as GNU Info in Docs/mysql.info and as PostScript in Docs/manual.ps. For a contributed user manual see http://www.turbolift.com/mysql. MySQL is brought to you by the MySQL team at MySQL AB For a list of developers and other contributors, see the Credits appendix in the manual. ************************************************************ IMPORTANT: Send bug (error) reports, questions and comments to the mailing list at mysql@lists.mysql.com Please use the 'mysqlbug' script when posting bug reports or questions about MySQL. mysqlbug will gather some information about your system and start your editor with a form in which you can describe your problem. Bug reports might be silently ignored by the MySQL maintainers if there is not a good reason included in the report as to why mysqlbug has not been used. A report that says 'MySQL does not work for me. Why?' is not consider a valid bug report. The mysqlbug script can be found in the 'scripts' directory in the distribution, that is 'there-you-installed-mysql/scripts'.