Proliferation of custom fields

[David Miller]

So, it shouldn't be any surprise that custom fields actually get used
now that they're available.  We're starting to add quite a few of them
for specific purposes at Mozilla.

When you add a custom field that isn't a multi-select or a map, (just a
string or a date for example) it gets added as a column to the bugs
table.  I've got a little voice in the back of my head telling me that's
going to hurt eventually if we keep adding fields.  Is my little voice
correct, or have I nothing to worry about?  Is there a better way to
architect it in the long run that won't cause as much damage?  Maybe a
second table for bugs_custom that is only joined once by bug_id and is
otherwise just custom fields for bugs?  That only buys you so much time,
too, but potentially less stress on things that look at bugs and don't
touch custom fields...

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/