Custom Fields again

Joel Peshkin bugreport at
Thu Dec 12 01:19:59 UTC 2002

Gervase Markham wrote:

> Joel Peshkin wrote:
>> Using localconfig solves several problems.  If I add a field using 
>> localconfig and run checksetup to get it into the DB, it clears up 
>> many migration issues that apply to fields added by sites using 
>> checksetup. 
> I don't understand what you mean here. Could you elaborate?


Currently, if I make my own site-specific DB fields in checksetup, I am 
itching for a merge conflict when I update.  If I define what I want to 
have added to the "stock" DB using localconfig, then I use a standard 
(unhacked) checksetup and I wont have a big merge mess when checksetup 
starts to be database-agnostic (because I haven't tweaked it there).   
After all, my schema changes "belong" in exactlt the same place in 
checksetup as the very next schema change done to the tip will edit.  I 
am guaranteed a conflict when I update.

More information about the developers mailing list