Project

General

Profile

Actions
Copy link

Defect #9219

closed

Plugin Conflicts

Added by Evan Davey about 13 years ago. Updated about 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Plugin API
Target version:
-
Start date:
2011-09-09
Due date:
% Done:

0%

Estimated time:
Resolution:
Wont fix
Affected version:

Description

Plugins should include their name in the prefix of database tables to avoid conflicts. This is a regular problem when installing multiple plugins as often they use the same table names e.g.: tags. The db:migrate_plugins script doesn't seem to handle this well and things get messy and out of sync.

Actions
Copy link
 #1

Updated by vikas singh about 13 years ago

  • Assignee set to Azamat Hackimov

-

Actions
Copy link
 #2

Updated by Etienne Massip about 13 years ago

  • Assignee deleted (Azamat Hackimov)
Actions
Copy link
 #3

Updated by Go MAEDA about 7 years ago

  • Category changed from Core Plugins to Plugin API
Actions
Copy link
 #4

Updated by Holger Just about 2 months ago

  • Status changed from New to Closed
  • Resolution set to Wont fix

Plugins are free top change about everything including adding arbitrary tables. While it';s certainly a good idea for plugins to prefix code modules, table names and columns with a unique prefix, this can not be comprehensively enforced.

If plugins are using the same (conflicting) names, these plugins need to be updated. But again: this is not something we could enforce as it would significantly restrict the flexibility of plugins.

Actions
Copy link

Also available in: Atom PDF