Closed Bug 409463 Opened 17 years ago Closed 17 years ago

The flagtypes.description DB format is not the same in an upgraded installation and in a fresh one

Categories

(Bugzilla :: Installation & Upgrading, defect)

3.1.2
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 3.2

People

(Reporter: LpSolit, Assigned: mkanat)

References

Details

(Keywords: regression)

Attachments

(1 file)

Bug 153129 incorrectly upgrades installations: >Index: Bugzilla/DB/Schema.pm >+ description => {TYPE => 'MEDIUMTEXT'}, >Index: Bugzilla/Install/DB.pm >+ $dbh->bz_alter_column('flagtypes', 'description', >+ { TYPE => 'MEDIUMTEXT', NOTNULL => 1 }); New installations have NOT NULL => 0 while upgraded ones have NOT NULL => 1.
Flags: blocking3.1.3+
Assignee: installation → mkanat
Attached patch v1Splinter Review
There's no reason to allow NULLs in the field, so the easiest solution is to make it NOTNULL. When creating new flag types, if you leave the description empty, they get an empty string for their description, not "NULL". So I'm just making the field NOT NULL and ensuring that upgrades work properly if there are any NULLs in the field.
Attachment #294390 - Flags: review+
Okay, I've tested this all sorts of ways and it seems to fix things as far as I can see.
Status: NEW → ASSIGNED
Flags: approval+
Checking in Bugzilla/DB/Schema.pm; /cvsroot/mozilla/webtools/bugzilla/Bugzilla/DB/Schema.pm,v <-- Schema.pm new revision: 1.95; previous revision: 1.94 done Checking in Bugzilla/Install/DB.pm; /cvsroot/mozilla/webtools/bugzilla/Bugzilla/Install/DB.pm,v <-- DB.pm new revision: 1.46; previous revision: 1.45 done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: