~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to drizzled/session.h

  • Committer: Brian Aker
  • Date: 2008-11-26 21:37:50 UTC
  • Revision ID: brian@tangent.org-20081126213750-m96j23htwfymuwlt
Collection of dead code removal

Show diffs side-by-side

added added

removed removed

Lines of Context:
1058
1058
    first_successful_insert_id_in_cur_stmt.
1059
1059
  */
1060
1060
  /*
1061
 
    stmt_depends_on_first_successful_insert_id_in_prev_stmt is set when
1062
 
    LAST_INSERT_ID() is used by a statement.
1063
 
    If it is set, first_successful_insert_id_in_prev_stmt_for_binlog will be
1064
 
    stored in the statement-based binlog.
1065
 
    This variable is CUMULATIVE along the execution of a stored function or
1066
 
    trigger: if one substatement sets it to 1 it will stay 1 until the
1067
 
    function/trigger ends, thus making sure that
1068
 
    first_successful_insert_id_in_prev_stmt_for_binlog does not change anymore
1069
 
    and is propagated to the caller for binlogging.
1070
 
  */
1071
 
  bool       stmt_depends_on_first_successful_insert_id_in_prev_stmt;
1072
 
  /*
1073
1061
    List of auto_increment intervals reserved by the thread so far, for
1074
1062
    storage in the statement-based binlog.
1075
1063
    Note that its minimum is not first_successful_insert_id_in_cur_stmt:
1126
1114
  }
1127
1115
  inline uint64_t read_first_successful_insert_id_in_prev_stmt(void)
1128
1116
  {
1129
 
    if (!stmt_depends_on_first_successful_insert_id_in_prev_stmt)
1130
 
    {
1131
 
      stmt_depends_on_first_successful_insert_id_in_prev_stmt= 1;
1132
 
    }
1133
1117
    return first_successful_insert_id_in_prev_stmt;
1134
1118
  }
1135
1119
  /*