> Rob van Maris wrote: > > 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
Okay, the fix I did is not how it is supposed to be then. I reversed it. It is a little confusing that the Storage and SearchQuery have both a method to escape fields. I based my fix on the SearchQuery version which I came across when I had some weird errors. Maybe, the old database files of the project had more disallowed fields then there are in the database files of 1.7. Are all files under org.mmbase.storage still in use? It took me a lot of time to find out where what was happening. And are the files in config.databases still required? Nico Klasens Finalist IT Group Java Specialists
