Demo Data isn't loaded in openupgrade server while updating

Bug #1192094 reported by Sylvain LE GAL (GRAP)
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenUpgrade Server
New
Medium
Unassigned

Bug Description

Hi,

I continue to work on script migration and I wanted to use demo data in 6.1 & 7.0 to see if all is operational after the migration.
(I don't know how the team members work to test script migration...)
So I have a problem when updating DB with demo data.

User case :
- Created DB in 6.1
-> with demo data.
-> without module installed.

updating this DB using openobject-upgrade :
I have a fatal error when updating my DB in v7.0
Extract of my log :
INFO v61_vierge_demo openerp.modules.loading: module base: loading res/res_partner_demo.yml
INFO v61_vierge_demo openerp.modules.loading: module base: loading res/res_partner_image_demo.xml
[...]
Parse error in ~/openobject-server_upgrade/openerp/addons/base/res/res_partner_image_demo.xml:17:
<record id="base.res_partner_address_5" model="res.partner">
<field name="image">iVB....</field>
</record>
[...]
IntegrityError: null value in column "name" violates not-null constraint

the #res_partner_address_5 is a new demo data of V7 and the creation is defined in the res_partner_demo.yml, that is parsed before but openUgrade don't create the res.partner "Chao Wang"

If I use openupgrade-server like a normal server and create a New DB v7 with demo data, the res_partner_address_5 ("Chao Wang") exists in the DB.

If it's a bug, i could be problematic. Not concerning demo data but other data.

Thanks for your attention.

Revision history for this message
Stefan Rijnhart (Opener) (stefan-opener) wrote :

One thing to note, is that demo data between two major releases of OpenERP is usually incompatible. We had a stanza in the migration script of 6.1/base to set demo to False in every module, thereby disabling the loading of the additional demo data of 6.1 on top of the 6.0 data. We should have it in 7.0 as well, I believe.

But in this case, the record itself does not exist, as it is not referenced in the 6.1 demo data. So it seems interesting enough to check it out when convenient. Thanks for reporting!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.