MySQL Bugs: #25266: Behaviour changed doing 'Apply Changes' in MySQL Table Editor

Bug #25266	Behaviour changed doing 'Apply Changes' in MySQL Table Editor
Submitted:	24 Dec 2006 16:53	Modified:	17 Jan 2007 15:55
Reporter:	Heinz Schweitzer (Gold Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.8	OS:	Windows (Windows XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Behaviour changed doing 'Apply Changes' in MySQL Table Editor

In previous releases some window poped up saying something similar 
'your changes made do not require modification on table ' 
This is no longer the case.
From now on you will be presented with a regular SQL execution dialog. 

MySQL Server Information
--------------------------------------------------------------------------------
Connected to MySQL Server Instance
  Username:                root
  Hostname:                localhost
  Port:                    3306
--------------------------------------------------------------------------------
Server Information
  MySQL Version:           MySQL 5.0.24a-community-nt via TCP/IP
  Network Name:            localhost
  IP:                      127.0.0.1
--------------------------------------------------------------------------------
Client Information
  Version:                 MySQL Client Version 5.1.11
  Network Name:            hgs
  IP:                      192.168.2.5
  Operating System:        Windows XP
  Hardware:                Intel(R) Pentium(R) 4 CPU 2.00GHz, 504 MB RAM

How to repeat:
Open MySQL Administrator 
In Cataolgs select schame mysql
In the right pane select table db and say edit.
MySQL Table Editor pops up.
In there, for field Host uncheck then chack again the 'Not Null'
flag.
Press the 'Applay Changes' button.
The Confirm Table Edit dialog comes up like in screen shot a1.

New feature ??

a1

Attachment: a1.png (image/png, text), 112.40 KiB.

Thank you for a problem report. Verified just as described.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html