The Road to 2.18 - Customfields

Daniel Berlin dberlin at
Fri Mar 12 19:53:16 UTC 2004

On Mar 12, 2004, at 2:34 PM, Stuart Donaldson wrote:

> 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.
> There has been concern about the number of tables and left-joins 
> involved with custom fields.

Well, Sean obviously has a working implementation of this.
Sean, how many bugs does your install have?
What is performance like on your database for queries against multiple 
custom fields?

More information about the developers mailing list