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
520365fe
Commit
520365fe
authored
Mar 31, 2008
by
unknown
Browse files
Options
Browse Files
Download
Plain Diff
Merge mkindahl@bk-internal.mysql.com:/home/bk/mysql-5.1-bugteam
into mats-laptop.(none):/home/bk/b29020-mysql-5.1-rpl
parents
f6229d3d
600a664a
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
24 additions
and
8 deletions
+24
-8
mysql-test/include/commit.inc
mysql-test/include/commit.inc
+12
-4
mysql-test/r/commit_1innodb.result
mysql-test/r/commit_1innodb.result
+12
-4
No files found.
mysql-test/include/commit.inc
View file @
520365fe
...
@@ -542,17 +542,25 @@ call p_verify_status_increment(0, 0, 0, 0);
...
@@ -542,17 +542,25 @@ call p_verify_status_increment(0, 0, 0, 0);
--
echo
# 16. A function changes non-trans-table.
--
echo
# 16. A function changes non-trans-table.
--
echo
#
--
echo
#
--
echo
# For row-based logging, there is an extra commit for the
--
echo
# non-transactional changes saved in the transaction cache to
--
echo
# the binary log.
--
echo
#
select
f1
();
select
f1
();
call
p_verify_status_increment
(
0
,
0
,
0
,
0
);
call
p_verify_status_increment
(
0
,
0
,
1
,
0
);
commit
;
commit
;
call
p_verify_status_increment
(
0
,
0
,
0
,
0
);
call
p_verify_status_increment
(
0
,
0
,
1
,
0
);
--
echo
# 17. Read-only statement, a function changes non-trans-table.
--
echo
# 17. Read-only statement, a function changes non-trans-table.
--
echo
#
--
echo
#
--
echo
# For row-based logging, there is an extra commit for the
--
echo
# non-transactional changes saved in the transaction cache to
--
echo
# the binary log.
--
echo
#
select
f1
()
from
t1
;
select
f1
()
from
t1
;
call
p_verify_status_increment
(
1
,
0
,
1
,
0
);
call
p_verify_status_increment
(
1
,
0
,
2
,
0
);
commit
;
commit
;
call
p_verify_status_increment
(
1
,
0
,
1
,
0
);
call
p_verify_status_increment
(
1
,
0
,
2
,
0
);
--
echo
# 18. Read-write statement: UPDATE, change 0 (transactional) rows.
--
echo
# 18. Read-write statement: UPDATE, change 0 (transactional) rows.
--
echo
#
--
echo
#
...
...
mysql-test/r/commit_1innodb.result
View file @
520365fe
...
@@ -571,27 +571,35 @@ SUCCESS
...
@@ -571,27 +571,35 @@ SUCCESS
# 16. A function changes non-trans-table.
# 16. A function changes non-trans-table.
#
#
# For row-based logging, there is an extra commit for the
# non-transactional changes saved in the transaction cache to
# the binary log.
#
select f1();
select f1();
f1()
f1()
2
2
call p_verify_status_increment(0, 0,
0
, 0);
call p_verify_status_increment(0, 0,
1
, 0);
SUCCESS
SUCCESS
commit;
commit;
call p_verify_status_increment(0, 0,
0
, 0);
call p_verify_status_increment(0, 0,
1
, 0);
SUCCESS
SUCCESS
# 17. Read-only statement, a function changes non-trans-table.
# 17. Read-only statement, a function changes non-trans-table.
#
#
# For row-based logging, there is an extra commit for the
# non-transactional changes saved in the transaction cache to
# the binary log.
#
select f1() from t1;
select f1() from t1;
f1()
f1()
2
2
2
2
call p_verify_status_increment(1, 0,
1
, 0);
call p_verify_status_increment(1, 0,
2
, 0);
SUCCESS
SUCCESS
commit;
commit;
call p_verify_status_increment(1, 0,
1
, 0);
call p_verify_status_increment(1, 0,
2
, 0);
SUCCESS
SUCCESS
# 18. Read-write statement: UPDATE, change 0 (transactional) rows.
# 18. Read-write statement: UPDATE, change 0 (transactional) rows.
...
...
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