diff options
author | Daniel Bartholomew <dbart@askmonty.org> | 2012-06-18 16:57:58 -0400 |
---|---|---|
committer | Daniel Bartholomew <dbart@askmonty.org> | 2012-06-18 16:57:58 -0400 |
commit | bdc68e5baf9eafdc1956ff555770b010a6260102 (patch) | |
tree | 02eda0c162de39761ea7bdef50f464869255c9ce /KNOWN_BUGS.txt | |
parent | 28f2c5641d2b1423f4904828a678ceb3e794355e (diff) | |
download | mariadb-git-bdc68e5baf9eafdc1956ff555770b010a6260102.tar.gz |
various documentation updates
Diffstat (limited to 'KNOWN_BUGS.txt')
-rw-r--r-- | KNOWN_BUGS.txt | 50 |
1 files changed, 25 insertions, 25 deletions
diff --git a/KNOWN_BUGS.txt b/KNOWN_BUGS.txt index 38472fc978c..56c9102b0cd 100644 --- a/KNOWN_BUGS.txt +++ b/KNOWN_BUGS.txt @@ -1,35 +1,35 @@ -This file should contain all know fatal bugs in the Mariadb and the -Maria storage engine for the last source or binary release. Minor -bugs, extensions and feature request and bugs found since this release -can be find in the MariaDB bugs database at: -https://bugs.launchpad.net/maria and in the MySQL bugs databases at: -http://bugs.mysql.com/ (category "Maria storage engine"). +This file should contain all known fatal bugs in Mariadb and the Aria +storage engine for the last source or binary release. Minor bugs, +extensions and feature requests, and bugs found since this release can +be found in the MariaDB bugs database at: http://mariadb.org/jira and +in the MySQL bugs databases at: http://bugs.mysql.com/ (category +"Maria storage engine"). -There shouldn't normally be any bugs that affects normal operations in -any MariaDB release. Still, there are always exceptions and edge cases -and that's what this file is for. +There should not normally be any bugs which affect normal operations +in any MariaDB release. Still, there are always exceptions and edge +cases and that is what this file is for. If you have found a bug that is not listed here, please add it to -http://bugs.launchpad.net/maria so that we can either fix it for next -release or in the worst case add it here for others to know! +http://mariadb.org/jira so we can either fix it for next release or in +the worst case add it here for others to know! + IMPORTANT: -If you have been using the Maria storage engine with -MySQL-5.1-Maria-alpha build and upgrading to a newer MariaDB you MUST -run maria_chk --recover on all your Maria tables. This is because we -made an incompatible change of how transaction id is stored and old -transaction id's must be reset! +If you have been using the Maria (now Aria) storage engine with the +MySQL-5.1-Maria-alpha build and are upgrading to a newer MariaDB you +MUST run [m]aria_chk --recover on all your Aria tables. This is because +we made an incompatible change with how the transaction id is stored +and old transaction id's must be reset! cd mysql-data-directory -maria_chk --recover */*.MAI +aria_chk --recover */*.MAI -As the Maria storage engine is now in beta we will do our best to not -introduce any incompatible changes in the data format for the Maria -tables; If this would be ever be needed, we will, if possible, support -both the old and the new version to make upgrades as easy as possible. +Going forward, we will do our best to not introduce any incompatible +changes in the data format for Aria tables. If this would be ever be +needed, we will, if possible, support both the old and the new version +to make upgrades as easy as possible. -Note that for the MariaDB 5.1 release the Maria storage engine is -classified as 'beta'; It should work, but use it with caution. Please -report all bugs to https://bugs.launchpad.net/maria so that we can fix -them! +Note that for the MariaDB 5.1 release the Aria storage engine is +classified as 'beta'; It should work, but use it with caution. Please +report all bugs to http://mariadb.org/jira so we can fix them! |