Bug: major database/table upgrades

Running into an issue by removal of obsolete table fields leftover from 0.9x. Causes an issue with $cb->insertObject since it fails with a field which doesn't exist in the target table. Not sure if this is a 'feature' or a 'bug'

Before moving to beta or definitley rc state, we need to resolve what we can do to alleviate this issue:

• keep obsolete fields in critical tables
• do a check to remove 'absent' fields before doing a 'restore database' operation
• do a check to remove 'absent' fields before insertObject

Secondary issue is should we call it 'container2' or simply 'comtainer'. The latter might help compensate for other issues since it might appear to be a containermodule reference. Again, something to be resolved before moving to a new code state.