Hi, as part of the Drupal administration user experience survey we are improving the upgrade instructions for Drupal. This was listed as the 5th most difficult administration task. During interviews with administrators we learned that people want to know if they need to upgrade their database or just apply new files as in the recent security releases. I have created a page: Do I need upgrade my database? http:// drupal.org/node/37017 I was told that the changelog ( http://drupal.org/CHANGELOG.txt ) contained this information. But it is not obvious to me. How do I create an official list of which releases require a DB update? Thanks, Kieran
On Wed, 9 Nov 2005, Kieran Lal wrote:
Hi, as part of the Drupal administration user experience survey we are improving the upgrade instructions for Drupal. This was listed as the 5th most difficult administration task.
During interviews with administrators we learned that people want to know if they need to upgrade their database or just apply new files as in the recent security releases.
I have created a page: Do I need upgrade my database? http:// drupal.org/node/37017
I was told that the changelog ( http://drupal.org/CHANGELOG.txt ) contained this information. But it is not obvious to me. How do I create an official list of which releases require a DB update?
Rule of thumb: Major releases have a db upgrade, minor ones don't. The latter was not true for the 4.6.1 release, I think. It was the first to break the rule, IIRC. Cheers, Gerhard
On Wed, 9 Nov 2005, Kieran Lal wrote:
On Nov 9, 2005, at 1:24 PM, Gerhard Killesreiter wrote:
Major releases have a db upgrade, minor ones don't.
What's the definite way to check for at least 4.5 and 4.6?
Read database/updates.inc and compare dates to release dates. You need to check them separately for each release to be really, really sure. Cheers, Gerhard
What we really need, IMO is a simple variable_get/set that contains the active version. Nothing too hard to code. WE can think of all osrts of fancy CVS integration and automated version upgrading stuff, but a simple string, one that appears in admin/help/version should do imo. unfortunately (hehe) I don't have time to code it, or better: to maintain a patch for this. Ber
Done we already have something similar? It is the date after which all updates should be applied. mysql> select * from variable where name like 'update_start'; +--------------+--------------------+ | name | value | +--------------+--------------------+ | update_start | s:10:"2005-03-21"; | +--------------+--------------------+ 1 row in set (0.00 sec) On 11/10/05, Bèr Kessels <ber@webschuur.com> wrote:
What we really need, IMO is a simple variable_get/set that contains the active version. Nothing too hard to code. WE can think of all osrts of fancy CVS integration and automated version upgrading stuff, but a simple string, one that appears in admin/help/version should do imo.
unfortunately (hehe) I don't have time to code it, or better: to maintain a patch for this.
Ber
On Wed, Nov 09, 2005 at 01:32:41PM -0800, Kieran Lal wrote:
On Nov 9, 2005, at 1:24 PM, Gerhard Killesreiter wrote:
Major releases have a db upgrade, minor ones don't.
What's the definite way to check for at least 4.5 and 4.6?
It could be done automatically, e.g. by storing drupal version in the database and having update.php check that version. -- Piotrek irc: #debian.pl Mors Drosophilis melanogastribus!
On 09 Nov 2005, at 13:24, Gerhard Killesreiter wrote:
On Wed, 9 Nov 2005, Kieran Lal wrote:
Hi, as part of the Drupal administration user experience survey we are improving the upgrade instructions for Drupal. This was listed as the 5th most difficult administration task.
During interviews with administrators we learned that people want to know if they need to upgrade their database or just apply new files as in the recent security releases.
I have created a page: Do I need upgrade my database? http:// drupal.org/node/37017
I was told that the changelog ( http://drupal.org/CHANGELOG.txt ) contained this information. But it is not obvious to me. How do I create an official list of which releases require a DB update?
Rule of thumb:
Major releases have a db upgrade, minor ones don't.
The latter was not true for the 4.6.1 release, I think. It was the first to break the rule, IIRC.
Speaking of such, I think there may be a lurking problem with the 4.6.x (where x>0) to 4.7 upgrade. IIRC, the mechanism for determining what updates need to be applied is a string >= comparison on the date of the update. The last update for 4.6.0 was "2005-03-21" (I think). Since then, there have been a number of updates in the 4.6.x trunk and a different sequence of updates in the 4.7 trunk. I think this creates the risk that some of the 4.7 upgrades (i.e. those with dates <= the 4.6.x upgrades) will get skipped. Has anyone verified that the 4.6.x -> 4.7 upgrade does in fact get all of the 4.7 schema updates? I can't; I just don't have time to spend on Drupal until well after the 4.7 release. -Eric
On Fri, Nov 11, 2005 at 09:45:56PM -0800, Eric Scouten wrote:
Speaking of such, I think there may be a lurking problem with the 4.6.x (where x>0) to 4.7 upgrade.
IIRC, the mechanism for determining what updates need to be applied is a string >= comparison on the date of the update.
The last update for 4.6.0 was "2005-03-21" (I think). Since then, there have been a number of updates in the 4.6.x trunk and a different sequence of updates in the 4.7 trunk. I think this creates the risk that some of the 4.7 upgrades (i.e. those with dates <= the 4.6.x upgrades) will get skipped.
Has anyone verified that the 4.6.x -> 4.7 upgrade does in fact get all of the 4.7 schema updates? I can't; I just don't have time to spend on Drupal until well after the 4.7 release.
I noticed this and provided a workaround in my giant update patch [1]. 1. http://drupal.org/node/35924 -Neil
participants (7)
-
B�r Kessels -
Eric Scouten -
Gerhard Killesreiter -
Khalid B -
Kieran Lal -
neil＠civicspacelabs.org -
piotr＠mallorn.ii.uj.edu.pl