MySQL Bugs: #44609: perfix arrangement throw error

Bug #44609	perfix arrangement throw error
Submitted:	1 May 2009 15:25	Modified:	1 Jun 2009 18:58
Reporter:	Yochai Akoka	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.1.30	OS:	Windows (Vista)
Assigned to:		CPU Architecture:	Any
Tags:	clause, INTEGER, Perfix

Description:
I noticed that when I used the following command: 
INSERT INTO `pages` (`someIntField`) VALUES('5')
it somehow worked, in contrast to the fact that it supposed to understand the different between an integer value to a string value. 
As you probably know, if I removed the inverted commas I would get an error. Another issue is some perfix arrangement that mysql do - 
If I remove the inverted commas and add another *string field after the integer field it will work just fine; 
all what I say is also true when I use where clause(when the last clause is on integer field).

How to repeat:
it can repeat everywhere, i dont realy hava time to check all the options but i'm pretty sure that in my description above you'll see that its realy a serius bug.

Thank you for the problem report. Please, send complete test case, with exact CREATE TABLE and INSERT statements. I don't see any problem with my 5.1.34:

valeriy-kravchuks-macbook-pro:5.1 openxs$ bin/mysql -uroot test
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.1.34-debug Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> create table tint(c1 int);
Query OK, 0 rows affected (0.06 sec)

mysql> insert into `tint`(`c1`) values ('5');
Query OK, 1 row affected (0.00 sec)

mysql> insert into tint(c1) values ('5');
Query OK, 1 row affected (0.00 sec)

Why do you think it should not work? String '5' is just converted into number, 5, implicitly.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".