Remove old updates that spanned several schema changes and require that database be current before upgrading to 6.x. This is needed because the CCK database has dramatically changed several times, including changing to and then away from table names that were later usurped by core. The 6.x structure finishes moving completely away from using table names prefixed with 'node_' to avoid future upgrade problems as core incorporates more parts of CCK.

This means 4.7 to 6.x upgrades will require an intermediate update to 5.x, and 5.x to 6.x upgrades will require that the latest code be used to upgrade the database in 5.x before upgrading to 6.x.

This won't be popular, but maintaining all those old updates to make sure that nothing breaks no matter what state the database is in has become an impossible task. Hopefully once everyone is stablized using the 6.x structure we can stick to automatic updates in the future.

Change the install files to avoid using content_alter_db_field() just to add a column and instead use Schema API. Also add better checks so older updates won't fire when the tables and columns don't exist.

Make sure schema gets refreshed when field types change! More changes to remove use of #field in elements and replace it with new #field_info value in $form; Move install, uninstall, enable, and disable hooks all into .install file; Start developer upgrade documentation.

Add updates to install files to alter all columns to default to NULL values. Need to come back and update data, too.

Add content_notify() function modules can use to let content module take action when they are uninstalled or disabled. Change all field columns to 'not null' = FALSE so we can search for empty values consistently across field types.

 are moved from 'node_' to 'content_' namespace)
+ fixes for older 4.7 versions migration path
update.php required !!

as a side effect.

requires running update.php.