hello developers

It used to be so that if you increase the version number on a builder
after adding some fields the configuration would be reevalueated and new
fields would be created in the database. This is no longer the case. 
What happens i think is that at mmbase startup time first the storage is
initiated, and storage is checking all the builders and find fields that
are not present in the database. Than it creates a virtual field for it
( VERIFY: Field 'naam' of builder 'aflevering' does NOT exist in
storage! Field will be considered virtual.)
Then the builders are initialized, and the versions are checked. But
even though some builders have a higher version than the installed one.
No 'new' fields are found.
Is this correct, or do i miss something. And if so, what could be a
quick workaround?
my mmbase version is 1.7.2.20041002


regards,

Ernst
_______________________________________________
Developers mailing list
[EMAIL PROTECTED]
http://lists.mmbase.org/mailman/listinfo/developers

Reply via email to