database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-11-09 11:41:36 +03:00
Code Activity

manual.texi minor change notes mods

Browse Source 
Docs/manual.texi:
  minor change notes mods
This commit is contained in:
unknown
2001-05-20 21:08:54 -05:00
parent 33db66b7c5
commit c5bcda50c5
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Docs/manual.texi
View File

@@ -44366,10 +44366,10 @@ releases of 3.23 with small fixes for this part of the code. As long as
you don't use these features, you should be quite safe with you don't use these features, you should be quite safe with
@strong{MySQL} 3.23! @strong{MySQL} 3.23!
Note that the above doesn't mean that replication or Berkeley DB doesn't Note that the above doesn't mean that replication or Berkeley DB don't
work; We have done a lot of testing of all code, including replication work; We have done a lot of testing of all code, including replication
and BDB without finding any problems. It only means that not as many and BDB without finding any problems. It only means that not as many
users uses this code as the rest of the code and because of this we are users use this code as the rest of the code and because of this we are
not yet 100% confident in this code. not yet 100% confident in this code.
@menu @menu
@@ -44450,8 +44450,8 @@ Added option @code{--skip-stack-trace} to @code{mysqld}.
@item @item
Added option @code{CONCURRENT} to @code{LOAD DATA}. Added option @code{CONCURRENT} to @code{LOAD DATA}.
@item @item
Better error message when slave @code{max_allowed_packet} is to low to Better error message when slave @code{max_allowed_packet} is too low to
read a very long log event from the master read a very long log event from the master.
@item @item
Fixed bug when too many rows where removed when using Fixed bug when too many rows where removed when using
@code{SELECT DISTINCT ... HAVING}. @code{SELECT DISTINCT ... HAVING}.