Custom fields schema

Gervase Markham gerv at
Thu Dec 16 00:10:59 UTC 2004

Sean McAfee wrote:
> Except for logging, I've never had much trouble with the two distinct
> tables.

As this was a sticking point last time around, I should just mention - 
the solution should have one single table for tracking bug changes, not 
two. If that requires enhancing the existing one, that's absolutely fine.

> Besides, they describe two different kinds of data; FIELDDEFS
> describes columns of the BUGS table, but CUSTOM_FIELDS describes data that
> lives in the various CF_* tables.  Some FIELDDEFS columns are even computed,
> such as "Days since bug changed", a concept which can't apply to custom
> fields as currently defined.

I think you may be confusing the fielddefs table with another one. 
fielddefs does not have a "Days since bug changed" column, it has 
fieldid, name, description, mailhead (which needs to die) and sortkey.

>>Also, do we need accesskeys for customfields? 
> Er...what are they?

HTML accesskeys. And the answer is no; we're moving away from them, 
because most people don't use them, and they annoy many keyboard users.


More information about the developers mailing list