[MDEV-6009] MySQL Bug#13819100 BROKEN SYNTAX ACCEPTED FOR START SLAVE, STOP SLAVE Created: 2014-04-02  Updated: 2022-09-08

Status: Open
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.10
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Sergey Vojtovich Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
PartOf
is part of MDEV-4784 merge test cases from 5.6 Stalled

 Description   

revno: 3690.1.38
committer: Marc Alff <marc.alff@oracle.com>
branch nick: mysql-trunk-bug13819100
timestamp: Wed 2012-03-07 17:15:16 +0100
message:
  Bug#13819100 BROKEN SYNTAX ACCEPTED FOR START SLAVE, STOP SLAVE
 
  Before this fix, the parser accepted the following syntax for STOP SLAVE:
 
  STOP SLAVE ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ;
 
  The root cause was the bison grammar for rule slave_thread_opts,
  which produced a list of "SQL_THREAD", "RELAY_THREAD" or (empty string),
  separated by ",".
 
  The grammar has been fixed so that the grammar rule is:
  - either en empty string
  - or a list of "SQL_THREAD", "RELAY_THREAD" separated by ",".
  which is the proper syntax.
 
  In addition, the grammar rules have been cleaned up, so that, when practical:
  - (a) using the bison internal stack ($$, $1, etc) is preferred
  - (b) setting global variables in rules, as in Lex->slave_thd_opt= ...
    is avoided
  Bison is an ascendent parser, for which the natural pattern in (a).
  Pattern (b) is for descendent parsers, and mixing both concepts is a bad
  idea.
 
  Note that using the same option multiple times in the list is tolerated,
  as before, and interpreted as a single option (no change).


Generated at Thu Feb 08 07:08:41 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.