← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to drizzled/sql_delete.cc

  • Committer: Brian Aker
  • Date: 2008-11-12 01:27:19 UTC
  • Revision ID: brian@tangent.org-20081112012719-rz97qt34iii2f73o
Next pass in removing/standardizing replication

Show diffs side-by-side

added added

removed removed

Lines of Context:
drizzled/sql_delete.cc
372
372
  
373
373
  List<Item> all_fields;
374
374
 
375
 
  /*
376
 
    Statement-based replication of DELETE ... LIMIT is not safe as order of
377
 
    rows is not defined, so in mixed mode we go to row-based.
378
 
 
379
 
    Note that we may consider a statement as safe if ORDER BY primary_key
380
 
    is present. However it may confuse users to see very similiar statements
381
 
    replicated differently.
382
 
  */
383
 
  if (session->lex->current_select->select_limit)
384
 
  {
385
 
    session->lex->set_stmt_unsafe();
386
 
    session->set_current_stmt_binlog_row_based();
387
 
  }
388
375
  session->lex->allow_sum_func= 0;
389
376
  if (setup_tables_and_check_access(session, &session->lex->select_lex.context,
390
377
                                    &session->lex->select_lex.top_join_list,