Red Hat Bugzilla – Bug 455800
Update database during migration to change NULL resolution values to empty string
Last modified: 2013-06-24 00:04:25 EDT
Description of problem: Update db_fixup.sql to change all NULL resolution values in the bugs table to empty strings to match the format 3.2 is expecting. Eventually this will be fixed back to NULL along with the upstream.
Created attachment 312087 [details] Patch to update bugs.resolution to empty string during database migration (v1)
Comment on attachment 312087 [details] Patch to update bugs.resolution to empty string during database migration (v1) Tony please verify that this looks okay. Thanks Dave
Comment on attachment 312087 [details] Patch to update bugs.resolution to empty string during database migration (v1) >Index: redhat/db_fixup.sql >=================================================================== >RCS file: /cvs/qa/rh_bugzilla_3/redhat/db_fixup.sql,v >retrieving revision 1.13 >diff -u -r1.13 db_fixup.sql >--- redhat/db_fixup.sql 26 Jun 2008 15:51:41 -0000 1.13 >+++ redhat/db_fixup.sql 17 Jul 2008 22:34:31 -0000 >@@ -331,4 +331,9 @@ > > --- Create new columns in fielddefs needed for public custom field support > ALTER TABLE fielddefs ADD COLUMN public tinyint(4) NOT NULL default '0'; >+ >+--- Update bugs table, set NULL resolution values to empty string >+UPDATE bugs SET resolution = '' WHERE resolution = NULL; --- xxx-tfu: Mysql uses "IS NULL" rather than "=null" to check NULL value, so the above query should be --- UPDATE bugs SET resolution = '' WHERE resolution IS NULL; >+ALTER TABLE bugs MODIFY resolution VARCHAR(64) NOT NULL DEFAULT ''; >+ >
Created attachment 312098 [details] Patch to update bugs.resolution to empty string during database migration (v2) Ugh, I knew that but went brain dead when I wrote that. Good catch. Here is an updated patch. Thanks Dave
Checked in fix to redhat/db_fixup.sql for this.
Pushed to partner-bugzilla.redhat.com today.