Forum OpenACS Development: Problem calling content_item__delete()

Collapse
1: Problem calling content_item__delete()
Posted by Peter Alberer on 04/06/04 03:24 PM

When calling content_item__delete() i get an error from the after delete trigger for the cr_revisions table (cr_revision_del_rev_ri_trg).

ERROR: Referential Integrity: attempting to delete live_revision: 213142

This is with postgres 7.4.1. The cr-triggers do not seems to have changed since quite some time, so i suppose the problem is based on some change in postgres. In content_item__delete() the function acs_object__delete is called for every revision and fails because the trigger does not allow to remove the live revision.

I thought that every function was one transaction and that all the triggers are running at the end of the function?! If this was the case the trigger should run at the end of content_item__delete where the content item itself should be deleted as well. But it seems as if the trigger is running immediately after the revision is removed.

When setting live_revision = null and latest_revision = null prior to removing the revisions the problem goes away.

Collapse
3: Re: Problem calling content_item__delete() (response to 1)
Posted by Peter Alberer on 04/06/04 03:39 PM
hmmm very interesting. i have another database (also pg741) with a openacs installation from a few weeks earlier and there the problem is not present. But i cannot find a difference in the functions involved...
Collapse
2: Re: Problem calling content_item__delete() (response to 1)
Posted by Dave Bauer on 04/06/04 03:47 PM
Right.

I think this is how it is supposed to work. The function does not let you delete the live revision.

Maybe an optional delete_live_revision_p parameter is in order?

Collapse
5: Re: Problem calling content_item__delete() (response to 2)
Posted by Peter Alberer on 04/06/04 03:53 PM
<blockquote>I think this is how it is supposed to work. The function does not let you delete the live revision
</blockquote>

Are you sure? I think the content_item__delete() function should not care about whether it is removing the live revision?! I think there is some error in my second installation or something has changed in the relevant parts of the code...

Collapse
4: Re: Problem calling content_item__delete() (response to 1)
Posted by Dave Bauer on 04/06/04 03:50 PM
Ah that is interesting. If I recall I can delete items via webdav without getting that error message.

Are you using an existing package, or your own code to do the deleting?

Collapse
6: Re: Problem calling content_item__delete() (response to 4)
Posted by Peter Alberer on 04/06/04 04:02 PM
<blockquote>Are you using an existing package, or your own code to do the deleting?
</blockquote>

I am using the standard "content_item__delete()" function to remove the content items. Other data for the object is stored in custom tables, but that is removed prior to calling content_item__delete() and does not cause the problem.

Collapse
7: Re: Problem calling content_item__delete() (response to 1)
Posted by Dave Bauer on 04/06/04 04:14 PM
Right. Is your call to db_exec_plsql in a db_transaction or another function call? Just calling db_exec_plsql query_name "select content_item__delete(:item_id)" seems to work.
Collapse
8: Re: Problem calling content_item__delete() (response to 1)
Posted by Peter Alberer on 04/06/04 04:21 PM
I am testing this from the psql command shell and call "select content_item__delete(SOMEID)" directly. But it is quite likely that you cannot reproduce the error as even in the first of my dbs it does not come up :) GRR, i think i will have to dig deeper into the cr-triggers, as the db where it does not work is my production database.
Collapse
9: Re: Problem calling content_item__delete() (response to 1)
Posted by Jun Yamog on 04/12/04 09:53 AM
You mean to say that its not consistent?  I thought it was, so in bcms I modified content_item__delete to set them to null.