#9 Failed upgrade from 0.7 svn version to 0.7 stable version, missing UPDATE-v0.7.sql file

[Viktor]

Upgrading from previous version fails on a few tables when checking "Verify Database".

Can't update the SQL via site/upgrade/index.php. It only says that no upgrade is necessary. Even though the "Verify Database" alternative says I have some missing tables. I used the SVN 0.7 version before the new stable version was released.

I managed to create the missing tables manually by reading the "SCHEMA.sql" file. This is how I fixed the database:

mysql> use phpipam;
mysql> ALTER TABLE switches ADD type int(2) DEFAULT '0';
mysql> ALTER TABLE settings ADD printLimit int(4) unsigned DEFAULT '25';
mysql> ALTER TABLE settings ADD vlanDuplicate int(1) DEFAULT '0';
mysql> ALTER TABLE logs ADD ipaddr varchar(64) DEFAULT NULL;

Trying to import SCHEMA.sql clears all my previous settings/subnets because of the "DROP TABLE IF EXISTS" lines.

Making an UPDATE-v0.7.sql file would solve this for other people.

[Miha Petkovsek]

Hi Viktor,

development SVN gets updated with new tables/fields as new features are being implemented, so I don't see an option to create sql file for it or would have to do it for each time db gets updated.

Basically each SVN commit, that deals with database is commented with --- db update ---, so you can check svn logs for changes.

Also, for your example in UPDATE-v0.6.sql there are always all changes, so for devel version of 0.8 you can monitor UPDATE-v0.7.sql as all will be updated with SQL insert each time a change is made.

brm

[Viktor]

Ok, I think I tried importing the UPDATE-v0.6.sql to my database without success, not sure now as I did this before the holidays.

Thanks for your input though and hard work on this great application.