The Road to 2.18 - Customfields

David Miller justdave at
Fri Mar 12 20:08:21 UTC 2004

On 3/12/2004 12:32 PM -0600, Jon Tollefson wrote:

> On Fri, 2004-03-12 at 13:01, Christopher Hicks wrote:
>> On Fri, 12 Mar 2004, Joel Peshkin wrote:
>> > In many ways, Sean's approach is cleaner than addind a bunch of columns
>> > to the tables,
>> For instance, we would need to avoid custom columns conflicting with
>> future official columns which implies munging the custom columns with ugly
>> names and ugly is bad.  :)
> Might we want some of the official columns(eg. status whiteboard,
> keywords, target milestone, qa contact, etc) to be implemented as custom
> fields?  Then sites could easily remove those fields if they didn't need
> them.

Yes, that's been the plan, which is why I'm worried about performance
impact on table joins.  We've been intending that several of the existing
columns which were capable of being defined within the custom fields
framework would be converted to custom fields so that they could be removed
by people that don't want them.  This means that people that don't remove
them would have a potential performance impact if custom fields don't
perform as well as the base fields do.
Dave Miller      Project Leader, Bugzilla Bug Tracking System   

More information about the developers mailing list