Issue 22 in power-matchmaker: Proofreaders/Critics integration with DQguru (Bugzilla #1626)
codesite...@google.com
Owner: mo.jeff
Labels: Type-Enhancement Priority-Medium Milestone-Release1.0 Component-UI
OpSys-All Usability
New issue 22 by mo.jeff: Proofreaders/Critics integration with DQguru
(Bugzilla #1626)
http://code.google.com/p/power-matchmaker/issues/detail?id=22
Original Description:
A check-as-you-work proofreader/critics system has been long proposed for
Power*Architect, and I think something similar for the Power*MatchMaker
would be really handy.
For example, both the Match and Merge engines perform some 'pre-fight'
checks before they start running. However, it would be handy if a critics
system monitored some of these things and visually warn the user. This
way, you wouldn't have to keep running the engine just to find out what's
wrong with your munge processes or merge rules.
This would be particularly useful for merge rules since it is possible for
derived merge rules to be not properly configured from the start (ex. a
merge rule derived for a table with no unique index defined).
This is related to Bug 945 for Power*Architect
http://trillian.sqlpower.ca/bugzilla/show_bug.cgi?id=945
So whoever implements the critics/proofreaders system, please keep this
idea in mind when designing so that we don't end up with a system that's
coupled with Power*Architect!
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings