credativ team mailing list archive

["Sylvain LE GAL \(GRAP\)" <sylvain.legal@xxxxxxxxx>]

Hi, 

I understand, your need is : Populate a 6.1 database to test openupgrade more easily. (Right no ?)

But the problem is that demo data are created by xml/yml file and have an xml_id. So during the migration, the data will be deleted if the data doesn't exist in 7.0. (and this is a case if you enable demo in 6.1 and disable demo in 7.0).

In a nutshell : 
1/ 6.1 (without demo) -> 7.0 (without demo) : it works ; 
2/ 6.1 (without demo) -> 7.0 (with demo) : I didn't test, but it should work ; 
3/ 6.1 (with demo) -> 7.0 (with / without demo) : it will not work ; 

A solution could be to detect demo data before the migration and delete the records of demo data (ir_model_data), to make them persistent. But there is no way to distinct demo data & "normal" data.
-- 
https://code.launchpad.net/~savoirfairelinux-openerp/openupgrade-server/NoDemo/+merge/193145
Your team OpenUpgrade Committers is subscribed to branch lp:openupgrade-server.