[OpenObject6] Synchronize Referential Settings violates not-null contsraint

[Zack Powers]

The column "company_id" now enforces a not null constraint on column.
To reproduce, use the following repositories:
bzr branch lp:openobject-server
bzr branch lp:openobject-addons
bar branch lp:openobject-addons/extra-5.0

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Wow crap!
This is because OpenERP S.A. just made it a required field. Previously we were asking the user to fill the shop.company_id field when trying to import orders (the shop company will then be copied into the sale order).

Now we have to do it differently.
May be we could associate the company related to the current user by default when creating the shop (there is no company concept inside Magento). The user could always change it afterwards.
In this case, we would need to clean up the shop.company_id check we recently introduced at order importation.
We should also take care to code it in a way that remain compatible with OpenERP v5 (no shop.company_id field).

Thanks for the report. You would help us by trying to create such a patch eventually.

[Zack Powers (zpowers)]

Here is a patch for getting company_id from the current user, still needs a condition for if company_id does not exsit for OpenERP 5.

[Zack Powers (zpowers)]

Cleaned up a print statement left in the last patch.

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Guys, it has been fixed a while ago already.