Simple: Reporting.
I didn't want to have the merge contents from multiple sources in order
to produce a report.
And the structure of the plexus-registry basically forced me into using
the configuration approach over the db approach.
- Joakim
Brett Porter wrote:
Hi,
Can someone explain the need for having the repository configuration
stored in the database?
I've observed that:
- it is only saved there from the configuration files
- it is never modified, nor does it store additional information than
in the configuration
- it is never removed
- it does not appear to be referenced from any other jdo queries
(except some constraint classes that in turn are not used)
- some of the fields are never referenced (only the id/name/url are)
We do a lot of looking up the list of repositories from the database,
which isn't as efficient as using the equivalent stuff already in
memory from the configuration. Is there any reason not to make a few
substitutions there?
Thanks,
Brett
