[Debian-sf-devel] migration from sf 2.5 to 2.6

[Mathieu Peltier]

Hi,

For info, it seems that there is a small error that prevents the db-upgrade.pl
script to make its work (migration from sf 2.5-29 to latest CVS version
2.6-13+).

The script fails because my old trove_treesums table contains a trove_cat_id (0)
that does not exist in the trove_cat table (I guess that this is a small bug of
the script db_trove_maint.php in sf 2.5-29, which fills the trove_treesums
table?).

--------------------------------------------------------------------------------
Adding integrity constraints between the Trove map tables.
NOTICE:  ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
NOTICE:  ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
NOTICE:  ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
NOTICE:  ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
NOTICE:  ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
DBD::Pg::st execute failed: ERROR:  trove_treesums_cat_id_fk referential 
integrity violation - key referenced from trove_treesums not found in trove_cat 
at ./db-upgrade.pl line 694.
Transaction aborted because Uncaught exception from user code:
        DBD::Pg::st execute failed: ERROR:  trove_treesums_cat_id_fk 
referential integrity violation - key referenced from trove_treesums not found 
in trove_cat at ./db-upgrade.pl line 694.
        eval {...} called at ./db-upgrade.pl line 42
Transaction aborted because Uncaught exception from user code:
        DBD::Pg::st execute failed: ERROR:  trove_treesums_cat_id_fk 
referential integrity violation - key referenced from trove_treesums not found 
in trove_cat at ./db-upgrade.pl line 694.
        eval {...} called at ./db-upgrade.pl line 42
Last SQL query was:
ALTER TABLE trove_treesums ADD CONSTRAINT trove_treesums_cat_id_fk FOREIGN KEY 
(trove_cat_id) REFERENCES trove_cat(trove_cat_id) MATCH FULL
(end of query)
Please report this bug on the Debian bug-tracking system.
Please include the previous messages as well to help debugging.
You should not worry too much about this,
your DB is still in a consistent state and should be usable.
--------------------------------------------------------------------------------

To solve this problem, I simply delete the record (trove_cat_id=0) in the
trove_treesums table before doing the update: 
delete from trove_treesums where trove_cat_id=0;

Then the upgrade seems to work fine. Perhaps this deletion should be add to the
db-upgrade.sh script?

best regards,

-- 
Mathieu Peltier
INRIA Rhône-Alpes - ObjectWeb Consortium
http://www.inrialpes.fr/ - http://www.objectweb.org/