Thanks for your quick reply. May we should not invest too much time, because my scenario is quite specific. I call the function "calendar::item::edit" from my own package (outside the calender package) to edit existing appointments in the personal calendar. Additionally to that, my package instance is mounted on three different site nodes. Altogether results in the described error.
Calling stack:
calendar::item::edit
=> calendar::do_notifications
=> calendar::item::get
=> calendar::attachments_enabled_p
=> site_node_apm_integration::child_package_exists_p
=> site_node_apm_integration::get_child_package_id (subquery will fail, db_transaction in calendar::item::edit will rollback)
An ugly hack would be to call "ad_conn -set package_id" with a different package_id prior call of calendar::item::edit. That would work, but I tried to avoid that.
Many thanks
Patrick
