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
ce765fb9
Commit
ce765fb9
authored
Jun 08, 2001
by
heikki@donna.mysql.fi
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
row0sel.c Fix a bug in consistent read through a secondary index
parent
ee93f7c1
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
3 additions
and
2 deletions
+3
-2
BitKeeper/etc/logging_ok
BitKeeper/etc/logging_ok
+1
-0
innobase/row/row0sel.c
innobase/row/row0sel.c
+2
-2
No files found.
BitKeeper/etc/logging_ok
View file @
ce765fb9
jani@janikt.pp.saunalahti.fi
jani@janikt.pp.saunalahti.fi
heikki@donna.mysql.fi
innobase/row/row0sel.c
View file @
ce765fb9
...
@@ -2207,11 +2207,11 @@ row_sel_get_clust_rec_for_mysql(
...
@@ -2207,11 +2207,11 @@ row_sel_get_clust_rec_for_mysql(
visit through secondary index records that would not really
visit through secondary index records that would not really
exist in our snapshot. */
exist in our snapshot. */
if
(
(
old_vers
||
rec_get_deleted_flag
(
rec
))
if
(
clust_rec
&&
(
old_vers
||
rec_get_deleted_flag
(
rec
))
&&
!
row_sel_sec_rec_is_for_clust_rec
(
rec
,
sec_index
,
&&
!
row_sel_sec_rec_is_for_clust_rec
(
rec
,
sec_index
,
clust_rec
,
clust_index
))
{
clust_rec
,
clust_index
))
{
clust_rec
=
NULL
;
clust_rec
=
NULL
;
}
}
}
}
*
out_rec
=
clust_rec
;
*
out_rec
=
clust_rec
;
...
...
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