Migration to 1.7

[Nico Klasens]

Hello developers,   The last couple of days, I have tried to migrate one of our latest projects to MMBase 1.7. The project uses the editwizards and rmmci as additional applications. After some small bug fixes in the MMBase sources and the project code the site is up and running again. I haven’t tested the full project, but I think it is working for more then 90%.   A couple of things I had to change in the project   - Application files should have the same name as the name inside. Hacks to rename the file to load first results in not loading at all. Application files should get a requirements tag. This is a very good improvement in deploying the applications. We had to do some renaming to integrate a couple of our component applications to get it running.   - Loading builders will now complain when the size of the field does not match the size in the database. I like it that MMBase is telling where the application can be improved.   - 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.   SearchQueries will now complain when the constraint is not valid for the type of the fields (eg pos=’1’ is not valid for an integer) It will fallback to a legacy constraints and continue. A nice improvement IMO.   Nico Klasens   Finalist IT Group Java Specialists