>> 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. >> >Is this behavour considered to be well? it seems to me like a big issue >with large clouds. I think everyone wants to migrate to 1.7 as soon as >possible, but having to change a given number of conlumns in the db >seems a non-trivial issue to me. How did this go at the vpro, who i >beleve have been migrated already. Can anybody say?
This behaviour will cause great problems for inherited database where changing fields is rather painful. We at the VPRO haven't migrated to 1.7 as it not a stable release yet. What we have done about a month ago is implemented directionality in relations. If the list of disallowed fields changes a lot for us, thereby generating conflicts with current fields then either there has to be a workaround or we won't implement 1.7 anytime soon. GrtX. Rico
