Autovacuum causes integrity errors in portal_wizard/portal_wizard_user deletion

[Marcel van der Boom (HS-Development BV)]

The autovacuum job in 7.0 which removes transient objects tries to remove records from portal_wizard with a statement like:

  delete from portal_wizard where id in (1,2,3)

This statement fails because it tries to set the field wizard_id to NULL in portal_wizard_user which is defined as not null

The effect is that the objects are never pruned.

Solution is either to allow null in the wizard_id field or do a cascade.

[Marcel van der Boom (HS-Development BV) (mrb)]

Another solution would be to delete the portal.wizard.user objects first, but I don't know if the order of objects can be specified for the autovacuum job

[Amit Parik (amit-parik)]

Fixes looks like correct, our core team will review it.

Thank you!

[Marcel van der Boom (HS-Development BV) (mrb)]

Can this be merge please? Fix is trivial.

[Landis (larnold)]

I am getting this error also. Can't find he root. Has been ongoing.

___________

delete from portal_wizard where id IN (1,2,3,4,5)

Traceback (most recent call last): File"...openerp/server/openerp/sql)db.py", line 226, in execute res = self._obj.execute(query,params) IntegrityError: null value in column "wizard_id" violates not-null constraint CONTEXT: SQL statement "UPDATE ONLY "public"."portal_wizard_user" SET "wizard_id" = NULL WHRE $1 OPERATOR(pg_catalog.=) "wizard id"

(see attached screen shot of latest Traceback)

?field.comment=I am getting this error also. Can't find he root

delete from portal_wizard where id IN (1,2,3,4,5)

Traceback (most recent call last): File"...openerp/server/openerp/sql)db.py", line 226, in execute res = self._obj.execute(query,params) IntegrityError: null value in column "wizard_id" violates not-null constraint CONTEXT: SQL statement "UPDATE ONLY "public"."portal_wizard_user" SET "wizard_id" = NULL WHRE $1 OPERATOR(pg_catalog.=) "wizard id"

(see attached screen shot of latest Traceback)

[Marcel van der Boom (HS-Development BV) (mrb)]

Landis,

The cause of this bug is that the database needs an 'on delete cascade' clause for a column (see the diff at the top of this bug report).
If you apply the patch manually the error will disappear.

I do not know why this has not been applied, it's trivial.

Can anyone from OpenERP comment on this?