redmine_knowledgebase
redmine_knowledgebase copied to clipboard
alexbevi
table prefix
Pet peeve: plugins that create tables should use their own plugin-specific prefix on their custom table names, rather than a "bare word" that might be used by someone else. Case in point: the CRM plugin, from the redminecrm.com folks, does similar tagging/tracking functions except as applied to Forum topics (presented as FAQs). They use "viewings" and "ratings" tables, which are presumably different than as needed by Knowledgebase. So if you already have CRM installed, your KB install fails.
KB should use kb_viewings and kb_ratings so as not to conflict. (And the CRM guys should use crm_ or faq_...)
I agree, and I'd like to change this in the future, but part of the problem is these acts_as_* gems are meant to be shared among implementations so the generic naming is actually a "feature".
The issue of busted plugin migrations due to insufficient requirements checks (or duplicated migrations) should be addressed in a way that ALL plugins can benefit.
