Hi

Dne Wed, 18 Aug 2010 08:51:16 -0400
Filipus Klutiero <chea...@gmail.com> napsal(a):

> Package: phpmyadmin
> Version: 4:3.3.5-1
> Severity: normal
> 
> MySQL returns success when trying to re-define a non-nullable column as 
> nullable if the column cannot be NULL due to it being part as a primary 
> key. This can be considered a bug or not, so feel free to reassign. As 
> http://dev.mysql.com/doc/refman/5.1/en/create-table.html says:
> 
> A |PRIMARY KEY| is a unique index where all key columns must be defined 
> as |NOT NULL|. If they are not explicitly declared as |NOT NULL|, MySQL 
> declares them so implicitly (and silently).
> 
> What is definitely a bug is phpmyadmin saying that "Table 
> tiki_user_watches has been altered successfully", when the table was not 
> altered.
> 
> For example, this was the query:
> |ALTER TABLE `tiki_user_watches` CHANGE `email` `email` VARCHAR( 200 ) 
> CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT ''|

In such case, MySQL command line client returns:

Query OK, 0 rows affected (0.05 sec)
Records: 0  Duplicates: 0  Warnings: 0

So it will as well tell you nothing about the problem.

Reassigning to MySQL as it should IMHO emit warning in this case.

-- 
        Michal Čihař | http://cihar.com | http://blog.cihar.com

Attachment: signature.asc
Description: PGP signature

Reply via email to