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
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
MariaDB
Commits
8c8f1886
Commit
8c8f1886
authored
Dec 07, 2004
by
gluh@gluh.mysql.r18.ru
Browse files
Options
Browse Files
Download
Plain Diff
Merge sgluhov@bk-internal.mysql.com:/home/bk/mysql-4.1
into gluh.mysql.r18.ru:/home/gluh/MySQL-BUGS/mysql-4.1.6077
parents
4458722f
8d70b2fc
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
4 deletions
+4
-4
mysql-test/t/key_cache.test
mysql-test/t/key_cache.test
+3
-3
sql/field.cc
sql/field.cc
+1
-1
No files found.
mysql-test/t/key_cache.test
View file @
8c8f1886
...
@@ -71,7 +71,7 @@ show status like 'key_blocks_used';
...
@@ -71,7 +71,7 @@ show status like 'key_blocks_used';
# Following results differs on 64 and 32 bit systems because of different
# Following results differs on 64 and 32 bit systems because of different
# pointer sizes, which takes up different amount of space in key cache
# pointer sizes, which takes up different amount of space in key cache
--
replace_result
1812
KEY_BLOCKS_UNUSED
1793
KEY_BLOCKS_UNUSED
1674
KEY_BLOCKS_UNUSED
1818
KEY_BLOCKS_UNUSED
--
replace_result
1812
KEY_BLOCKS_UNUSED
1793
KEY_BLOCKS_UNUSED
1674
KEY_BLOCKS_UNUSED
1818
KEY_BLOCKS_UNUSED
1824
KEY_BLOCKS_UNUSED
show
status
like
'key_blocks_unused'
;
show
status
like
'key_blocks_unused'
;
insert
into
t1
values
(
1
,
'qqqq'
),
(
11
,
'yyyy'
);
insert
into
t1
values
(
1
,
'qqqq'
),
(
11
,
'yyyy'
);
...
@@ -84,7 +84,7 @@ update t1 set p=2 where p=1;
...
@@ -84,7 +84,7 @@ update t1 set p=2 where p=1;
update
t2
set
i
=
2
where
i
=
1
;
update
t2
set
i
=
2
where
i
=
1
;
show
status
like
'key_blocks_used'
;
show
status
like
'key_blocks_used'
;
--
replace_result
1808
KEY_BLOCKS_UNUSED
1789
KEY_BLOCKS_UNUSED
1670
KEY_BLOCKS_UNUSED
1814
KEY_BLOCKS_UNUSED
--
replace_result
1808
KEY_BLOCKS_UNUSED
1789
KEY_BLOCKS_UNUSED
1670
KEY_BLOCKS_UNUSED
1814
KEY_BLOCKS_UNUSED
1820
KEY_BLOCKS_UNUSED
show
status
like
'key_blocks_unused'
;
show
status
like
'key_blocks_unused'
;
cache
index
t1
key
(
`primary`
)
in
keycache1
;
cache
index
t1
key
(
`primary`
)
in
keycache1
;
...
@@ -146,7 +146,7 @@ cache index t1,t2 in default;
...
@@ -146,7 +146,7 @@ cache index t1,t2 in default;
drop
table
t1
,
t2
,
t3
;
drop
table
t1
,
t2
,
t3
;
show
status
like
'key_blocks_used'
;
show
status
like
'key_blocks_used'
;
--
replace_result
1812
KEY_BLOCKS_UNUSED
1793
KEY_BLOCKS_UNUSED
1674
KEY_BLOCKS_UNUSED
1818
KEY_BLOCKS_UNUSED
--
replace_result
1812
KEY_BLOCKS_UNUSED
1793
KEY_BLOCKS_UNUSED
1674
KEY_BLOCKS_UNUSED
1818
KEY_BLOCKS_UNUSED
1824
KEY_BLOCKS_UNUSED
show
status
like
'key_blocks_unused'
;
show
status
like
'key_blocks_unused'
;
# Cleanup
# Cleanup
...
...
sql/field.cc
View file @
8c8f1886
...
@@ -2145,7 +2145,7 @@ int Field_longlong::store(double nr)
...
@@ -2145,7 +2145,7 @@ int Field_longlong::store(double nr)
set_warning
(
MYSQL_ERROR
::
WARN_LEVEL_WARN
,
ER_WARN_DATA_OUT_OF_RANGE
,
1
);
set_warning
(
MYSQL_ERROR
::
WARN_LEVEL_WARN
,
ER_WARN_DATA_OUT_OF_RANGE
,
1
);
error
=
1
;
error
=
1
;
}
}
else
if
(
nr
>=
(
double
)
LONGLONG_MAX
)
else
if
(
nr
>=
(
double
)
(
ulonglong
)
LONGLONG_MAX
)
{
{
res
=
(
longlong
)
LONGLONG_MAX
;
res
=
(
longlong
)
LONGLONG_MAX
;
set_warning
(
MYSQL_ERROR
::
WARN_LEVEL_WARN
,
ER_WARN_DATA_OUT_OF_RANGE
,
1
);
set_warning
(
MYSQL_ERROR
::
WARN_LEVEL_WARN
,
ER_WARN_DATA_OUT_OF_RANGE
,
1
);
...
...
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