Bug #34500 | Initial Inserts not automatically updated when changing a column name | ||
---|---|---|---|
Submitted: | 12 Feb 2008 19:39 | Modified: | 15 Mar 2008 12:47 |
Reporter: | Hugo Poissant | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.0.13 OSS Beta | OS: | Windows (XP Pro 2002 SP2) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
Tags: | inserts |
[12 Feb 2008 19:39]
Hugo Poissant
[12 Feb 2008 21:15]
Valeriy Kravchuk
Thank you for a problem report. Verified just as described.
[4 Mar 2008 20:18]
Johannes Taxacher
changing is fixed, but when you add a column (i.e. VARCHAR) then the inserts get corrupted because the column is added to the column-section but in the values-section only a comma is added without the '' for the empty value.
[5 Mar 2008 18:18]
Alfredo Kojima
I've changed it so that non-filled fields are set to NULL. It's expected that these INSERTs have to be eventually updated by the user.
[10 Mar 2008 14:56]
Johannes Taxacher
inserts are correctly updated when table-structure is changed (SVN 2692)
[15 Mar 2008 12:47]
MC Brown
A note has been added to the 5.15 changelog: Changing the column name of a table when you have pending inserts to the table did not change the column name in the corresponding INSERT statements.