Bug #12813 Instance Manager: START/STOP INSTANCE commands accept a list as argument

Submitted: 25 Aug 2005 19:31 Modified: 28 Feb 2006 2:48
Reporter: Alexander Nozdrin Email Updates:
Status: Closed Impact on me:
None 
Category:Instance Manager Severity:S3 (Non-critical)
Version:5.0 OS:
Assigned to: Petr Chardin CPU Architecture:Any

[25 Aug 2005 19:31] Alexander Nozdrin 
Description:
START/STOP INSTANCE commands are supposed to take an instance identifier as argument. Now they accept a list of identifiers as argument, while the action is performed only on the first item.

How to repeat:
START INSTANCE mysqld1, mysqld2, mysqld3;
STOP INSTANCE mysqld1, mysqld2, mysqld3;
[14 Feb 2006 0:07] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2556
[18 Feb 2006 0:26] Petr Chardin 
pushed into 5.0.19
[28 Feb 2006 2:43] Paul DuBois 
Noted in 5.0.19 changelog.

Instance Manager erroneously accepted a list of instance
identifiers for the <literal>START INSTANCE</literal> and
<literal>STOP INSTANCE</literal> commands (should accept only
a single identifier). (Bug #12813)

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.