RE: Migration to 1.7

[Rob van Maris]

Title: Message

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. If you made this change, I don't think it was a good idea in the first place, and you should consider undoing it, or provide a way to turn it off.   Rob van Maris Technical Consultant Quantiq xmedia & communication solutions Koninginneweg 11-13 1217 KP Hilversum T    +31 (0)356257211 M    +31 (0)651444006 E    [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nico Klasens Sent: woensdag 31 december 2003 11:54 To: [EMAIL PROTECTED] Subject: Migration to 1.7 - Storage and building queries has been changed and now the escaping of fields sometimes fails. I changed some code in the DatabaseStorageManagerFactory so the disallowed fields are generated from the sql92 keywords and the database metadata keywords. The DatabaseStorageManagerFactory already did the hard stuff, but didn’t use it at the end. Now a lot more columns are escaped then in MMBase 1.6 which results in a different database model. The constraints in the frontend sometimes fails, because they don’t have [] around the fieldnames. MMBase does not always complain about the fields and returns an empty list. I added [] on a couple of places and all the data was showing up again. I like it that the disallowed fields are generated by requesting it from the database, but this change in disallowed fields has big migration issues. Sites running on MMBase 1.6- have to change the database now.