2534
No check for auto events flag here - this write method should
2535
never be called if auto-events are enabled
2539
1. Write first log events which describe the 'run environment'
2544
If row-based binlogging, Insert_id, Rand and other kind of "setting
2545
context" events are not needed.
2549
if (!session->current_stmt_binlog_row_based)
2551
if (session->stmt_depends_on_first_successful_insert_id_in_prev_stmt)
2553
Intvar_log_event e(session,(unsigned char) LAST_INSERT_ID_EVENT,
2554
session->first_successful_insert_id_in_prev_stmt_for_binlog);
2558
if (session->auto_inc_intervals_in_cur_stmt_for_binlog.nb_elements() > 0)
2561
If the auto_increment was second in a table's index (possible with
2562
MyISAM or BDB) (table->next_number_keypart != 0), such event is
2563
in fact not necessary. We could avoid logging it.
2565
Intvar_log_event e(session, (unsigned char) INSERT_ID_EVENT,
2566
session->auto_inc_intervals_in_cur_stmt_for_binlog.
2571
if (session->rand_used)
2573
Rand_log_event e(session,session->rand_saved_seed1,session->rand_saved_seed2);
2577
if (session->user_var_events.elements)
2579
for (uint32_t i= 0; i < session->user_var_events.elements; i++)
2581
BINLOG_USER_VAR_EVENT *user_var_event;
2582
get_dynamic(&session->user_var_events,(unsigned char*) &user_var_event, i);
2583
User_var_log_event e(session, user_var_event->user_var_event->name.str,
2584
user_var_event->user_var_event->name.length,
2585
user_var_event->value,
2586
user_var_event->length,
2587
user_var_event->type,
2588
user_var_event->charset_number);
2597
2533
Write the SQL command