View Single Post
  #5  
Old 07-09-2011, 11:35 AM
wordmuse wordmuse is online now
Registered User
 
Join Date: 10-11-2006
Posts: 482
The correct way it should be done...

Customizations should be divided into two classes: global and database.

Global customizations ought to be stored separately from the databases and should apply to all databases unless...

Database customizations are in play and dictate something else.

This would be analogous to css styles in HTML documents. You can have a separate style sheet (here it would be a customization sheet) that is called by the html files (here, the databases).

But once an HTML file is opened, it can have styles that specifically override the external style sheet. Thus database customizations would override the global customizations.

I think this would solve the problem discussed here.
Reply With Quote