Bug #8296 VARBINARY: Silent data type change when size too large
| Submitted: | 3 Feb 2005 17:14 | Modified: | 12 May 2005 20:30 |
|---|---|---|---|
| Reporter: | Trudy Pelzer | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 5.0.3-alpha-debug | OS: | Linux (SuSE 9.1) |
| Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
[3 Feb 2005 17:14]
Trudy Pelzer
[10 Mar 2005 15:05]
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/internals/22899
[7 May 2005 14:51]
Trudy Pelzer
Per Monty's comment, the job is to: 1) If sql_mode='traditional', there is no column data type change. That is, the following returns an error: CREATE TABLE t1 (col1 VARBINARY(65537)); 2) If sql_mode='', there is a column data type change, with a warning generated: CREATE TABLE t1 (col1 VARBINARY(65537)); results in a col1 BLOB field and the current warning message.
[9 May 2005 16:07]
Ramil Kalimullin
Fixed in 5.0.6.
[12 May 2005 20:30]
Paul DuBois
Noted in 5.0.6 changelog and "silent column conversions" section.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.056 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.