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
47476652
Commit
47476652
authored
Nov 02, 2006
by
ramil/ram@myoffice.izhnet.ru
Browse files
Options
Browse Files
Download
Plain Diff
Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-5.1-maint
into mysql.com:/usr/home/ram/work/mysql-5.1-maint
parents
c8aa0948
26117992
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
8 additions
and
1 deletion
+8
-1
sql/opt_range.cc
sql/opt_range.cc
+5
-0
sql/opt_range.h
sql/opt_range.h
+3
-1
No files found.
sql/opt_range.cc
View file @
47476652
...
...
@@ -3237,6 +3237,11 @@ static bool create_partition_index_description(PART_PRUNE_PARAM *ppar)
key_part
->
field
=
(
*
field
);
key_part
->
image_type
=
Field
::
itRAW
;
/*
We set keypart flag to 0 here as the only HA_PART_KEY_SEG is checked
in the RangeAnalysisModule.
*/
key_part
->
flag
=
0
;
/* We don't set key_parts->null_bit as it will not be used */
ppar
->
is_part_keypart
[
part
]
=
!
in_subpart_fields
;
...
...
sql/opt_range.h
View file @
47476652
...
...
@@ -26,7 +26,9 @@
typedef
struct
st_key_part
{
uint16
key
,
part
,
store_length
,
length
;
uint8
null_bit
,
flag
;
uint8
null_bit
;
/* Keypart flags (0 if partition pruning is used) */
uint8
flag
;
Field
*
field
;
Field
::
imagetype
image_type
;
}
KEY_PART
;
...
...
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