Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
e5c2da01
Commit
e5c2da01
authored
Oct 02, 2002
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
manual.texi behavior -> behaviour
Docs/manual.texi: behavior -> behaviour
parent
00b8917c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
Docs/manual.texi
Docs/manual.texi
+4
-4
No files found.
Docs/manual.texi
View file @
e5c2da01
...
...
@@ -19931,7 +19931,7 @@ cache.
The value of the @code{--bdb-home} option.
@item @code{bdb_max_lock}
The maximum number of locks (1000 by default) you can have active on a
The maximum number of locks (10
,0
00 by default) you can have active on a
BDB table. You should increase this if you get errors of type @code{bdb:
Lock table is out of available locks} or @code{Got error 12 from ...}
when you have do long transactions or when @code{mysqld} has to examine
...
...
@@ -24212,7 +24212,7 @@ ignore, use the directive multiple times, once for each database.
You should not use this directive if you are using cross table updates
and you don't want these update to be replicated.
The main reason for this behavior is that it's hard from the command
The main reason for this behavio
u
r is that it's hard from the command
alone know if a query should be replicated or not; For example if you
are using multi-table-delete or multi-table-update commands in MySQL 4.x
that goes across multiple databases. It's also very fast to just check
...
...
@@ -31231,7 +31231,7 @@ mysql> SELECT IF(STRCMP('test','test1'),'no','yes');
If @code{expr2} or @code{expr3} is explicitely @code{NULL} then the
result type of the @code{IF()} function is the type of the not
@code{NULL} column. (This behavior is new in MySQL 4.0.3).
@code{NULL} column. (This behavio
u
r is new in MySQL 4.0.3).
@code{expr1} is evaluated as an integer value, which means that if you are
testing floating-point or string values, you should do so using a comparison
...
...
@@ -50996,7 +50996,7 @@ that can be used as data values in queries.
Changed variable @code{DELAY_KEY_WRITE} to an enum to allow one set
@code{DELAY_KEY_WRITE} for all tables without taking down the server.
@item
Changed behavior of @code{IF(condition,column,NULL)} so that it returns
Changed behavio
u
r of @code{IF(condition,column,NULL)} so that it returns
the value of the column type.
@item
Made @code{safe_mysqld} a symlink to @code{mysqld_safe} in binary distribution.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment