An alternate approach to custom fields

[David Miller]

On 3/22/03 10:03 AM +0000, Gervase Markham wrote:

> Jon Wilmoth wrote:
>
>> SortKey - Display order
>
> Where these have appeared elsewhere in Bugzilla, they have been a pain.
> Why is it needed?

fielddefs already has sort keys.  It's used to define the order the fields
are listed in when sending bugmail for new bugs.  That's not something new
he's adding.

>> Valexp - regular expression describing the valid pattern of input.  If
>> null, no validation is performed.  (also overrideable at lower level).
>
> Again, I'm not convinced we need this (other than the definition of enum
> types.)

I can see the use for this in general for strings....  say you put in a
free-text version number field because you have too many versions to list
in a popup.  Your version numbers are in a specific format that you can
always recognize though.  You could use this to ensure anything entered in
that field is actually a legal version number.

>> System - flag indicating this field is part of the base distribution and
>> must be present for the correct functioning of Bugzilla (i.e. a not
>> deletable flag).
>
> Surely the point of custom fields is that they are custom? Or is this a
> way to distinguish those fields currently in the fielddefs table from
> the new ones?

I think that's what he meant, since it was suggested to extend the existing
fielddefs table for that purpose.
-- 
Dave Miller      Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/             http://www.bugzilla.org/