From: Kenzaburo I. <ke...@30...> - 2003-08-26 16:50:22
|
Rodney, We've discussed this a bit a long while ago. The two big issues against were/are potential slowdowns from database access and localization headaches (primarily with enums, but also with translator updates). In the end, inertia won out and we stayed with what was in place. I completely agree that moving the configurations into the DB would be excellent from an administrative (and upgrade) viewpoint. Likewise for localization. For me it boils down to doing some performance testing and seeing if the results are acceptable. I'd like to put this as an official 'try it out' unless there are sound reasons to the contrary. Thanks, -Ken > Apologies if this has been brought up before, Ive not been on this > list very long. > > > Id like to propose an architectural change that would make mantis > easier to customize: > > o Move all field enumerations out of config files and into db tables. > o Create interface for managing the field enumerations. > > Status, Severity and Priority are some of the 'field enumerations' that > should be moved from config files into db tables. > > In fact, all config information could/should be moved into db tables. > Mantis would be much easier to configure and use if one does not have > to edit configuration files. > > One issue that we have found in our customization of mantis is the > requirement that the language files also be modified to correspond > to the changes made to the field enumerations. It would be nice if > a mantis admin could make the changes through an interface and have > the language strings 'automagically' updated. Maybe store the lang > strings in db tables ? > > > thanks > rodney |