#539: Product-scope TracAdmin commands don't take effect until tracd is
restarted
------------------------+-------------------------------
Reporter: rjollos | Owner: olemis
Type: defect | Status: accepted
Priority: major | Milestone: Release 6
Component: dashboard | Version:
Resolution: | Keywords: tracadmin command
------------------------+-------------------------------
Comment (by astaric):
Config values in Product Configuration are cached to avoid hitting the
database every time the config is accessed. Cache for config option is
invalidated only when this option is set using the same Configuration
instance, which is not the case when configuration is being changed using
the trac-admin.
Trac uses changes times of its configuration files to detect changes and
reload the configuration (it actually creates a new environment, see
open_environment in trac.env).
To provide similar behaviour for product configurations we would need to
somehow detect that the changes were made to the configuration in the
database. If could store last modification data as a special value in a
bloodhound_productconfig table, but this would require a hit to the
database each time a value is read from the config so simply disabling the
cache would be easier.
What was the reasoning behind the decision that the product configs should
be stored in the database instead of the .ini files? File configs would
allow us to reuse trac functionality for detecting modification of
configuration.
Anyway, I do not think that this issue is ready to be fixed before 0.6. We
can disable caching of config values which should be enough to close this
ticket and open a separate ticket for caching discussion, or move this
ticket to the next milestone.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/539#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
