then traceability and upgradeability is more difficult
Peter Apockotos wrote:
Why not just put in the version number in the footer each time you upgrade? Such as running Drupal 4.6.2
On Aug 1, 2005, at 3:48 PM, haisam@ido.org wrote:
Here are possible versioning tables, where one can track the current version and it's evolution. Perhaps one can also add the changelog in the versioning table.
CREATE TABLE `versioning` ( `id` INT NOT NULL auto_increment, `current_version` VARCHAR(255) NOT NULL, /* current version */ `date_of_version` DATETIME NOT NULL, /* date of version */ `date_of_install` TIMESTAMP(14) NOT NULL DEFAULT NOW(), PRIMARY KEY (`id` ), UNIQUE KEY `current` ( `current_version` ) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; ;
CREATE TABLE `versioning_relationship` ( `From_id1` INT NOT NULL, FOREIGN KEY (From_id1) REFERENCES versioning (id), `To_id2` INT NOT NULL, FOREIGN KEY (To_id2) REFERENCES versioning (id), PRIMARY KEY (`From_id1`, `To_id2` ) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Bèr Kessels wrote:
Go ahead and make a patch, if you really think it should be there. Op donderdag 28 juli 2005 15:47, schreef haisam@ido.org:
true, but that field should come from the db
Kobus Myburgh wrote:
Or be displayed somewhere in the admin section.
Kobus
>> haisam@ido.org 7/28/2005 3:43:06 PM >>> >>
The version should really be saved in the db.
Bill Fitzgerald wrote:
Dan KB6NU wrote:
> Is there an easy way to tell what version I'm running? > > Thanks, > > Dan >
Try reading the changelog.txt in the base directory of your drupal install -- the changelog will stop at your version.
Hope this helps.
Bill.
Regards, Bèr
-- [ Drupal support list | http://lists.drupal.org/ ]