This page details when a database upgrade is required - http://drupal.org/upgrade/do-i-upgrade-the-db
It needs details for the 4.7.x upgrades. My understanding is each update within the v4.7 release requires a database 'upgrade', but I could be incorrect. So the relevant page section could read:-
3a. If you are performing any of these upgrades, you do need to upgrade your database:
4.4.# to 4.5.#
4.5.# to 4.6.#
4.6.0 to 4.6.1 or higher
Any version to 4.7.0
Every upgrade from 4.7.0 a higher 4.7.x version will require a database upgrade.
And of course the upgrade from 4.7.x to V5 will require a database upgrade too.
"
If this is correct I'll have a go at editing that handbook page, if the appropriate permission is granted to me.
Comments
Comment #1
cog.rusty commentedThe answer to your question is here
http://cvs.drupal.org/viewcvs/drupal/drupal/database/database.4.1.mysql?...
but...
I don't think that handbook page is a good idea to exist. People should be advised to run /update.php as a standard ritual. If no database update is needed then none will be performed.
The answer to "should I run /update.php" should be always "yes", and nobody ever asks "should I upgrade my database"
The page is also likely to become obsolete (or else to become a small black hole for documentation work).
Sorry if I sound dismissive with your work, but sometimes it is good to take a step back and try to see if being thorough obscures the picture.
Comment #2
heine commentedI could not agree more with CogRusty; this page should be removed.
http://drupal.org/upgrade/getting-started may need some additional modifications to fit better in the chapter http://drupal.org/upgrade/tutorial-introduction
Comment #3
vjordan commentedWell we all agree this is confusing, which is a good starting point.
How about deleting page "do I upgrade the DB"? Then it would seem to make sense to collapse the http://drupal.org/upgrade/preparing-the-site page into the http://drupal.org/upgrade/getting-started so there are no child nodes on the latter.
What do you think?
Comment #4
heine commentedI figured that deleting the page could be a bit problematic due to all the crosslinks. I've edited the page to basically say; visit update.php (or check admin/logs/status).
Comment #5
vjordan commentedThis is closed so tidying up the status.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.