I am aware that the database metadata can be used to generate the keywords list, but it is precisely to avoid these kind of "migration" problems that I think a configurable list is a better solution.
This is also the reason why it was turned off (at least originally).
You can configure how you want disallowed fieldnames to be handled (to give an error, to be used as-is, or to be changed) in teh configuration file of the database (you will need to cahnge the databse resource, put it in the classes dir, and have mmabse.org point out the resource ).
See the org.mmbase.storage.Attributes javadoc for more information.
Gomez
