Commit ce529d83 authored by Zardosht Kasheff's avatar Zardosht Kasheff Committed by Yoni Fogel

addresses #686

add comments for several member variables

git-svn-id: file:///svn/mysql/tokudb-engine/src@3535 c7de825b-a66e-492c-adef-691d508d4ae1
parent 85aa7bfa
...@@ -36,9 +36,40 @@ private: ...@@ -36,9 +36,40 @@ private:
// TODO: make sure current_row gets set properly // TODO: make sure current_row gets set properly
// //
DBT current_row; DBT current_row;
//
// pointer used for multi_alloc of key_buff, key_buff2, primary_key_buff
//
void *alloc_ptr; void *alloc_ptr;
//
// buffer used to temporarily store a "packed row"
// data pointer of a DBT will end up pointing to this
// see pack_row for usage
//
uchar *rec_buff; uchar *rec_buff;
uchar *key_buff, *key_buff2, *primary_key_buff; //
// number of bytes allocated in rec_buff
//
ulong alloced_rec_buff_length;
//
// buffer used to temporarily store a "packed key"
// data pointer of a DBT will end up pointing to this
//
uchar *key_buff;
//
// buffer used to temporarily store a "packed key"
// data pointer of a DBT will end up pointing to this
// This is used in functions that require the packing
// of more than one key
//
uchar *key_buff2;
//
// buffer used to temporarily store a "packed key"
// data pointer of a DBT will end up pointing to this
// currently this is only used for a primary key in
// the function update_row, hence the name. It
// does not carry any state throughout the class.
//
uchar *primary_key_buff;
// //
// DB that is indexed on the primary key // DB that is indexed on the primary key
...@@ -67,7 +98,6 @@ private: ...@@ -67,7 +98,6 @@ private:
// flags that are returned in table_flags() // flags that are returned in table_flags()
// //
ulong int_table_flags; ulong int_table_flags;
ulong alloced_rec_buff_length;
// //
// count on the number of rows that gets changed, such as when write_row occurs // count on the number of rows that gets changed, such as when write_row occurs
// //
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment