CiviCRM Community Forums (archive)

We are (still  ) migrating a large database (+/- 1 million relationships) to CiviCRM. Now after the migration, we want to run job.disable_expired_relationships to change the status of all imported relationships with end_date in the past to inactive.

This seemed to cause a timeout; about 900000 of the relationships need to be updated.

I applied a rather simple patch to our CiviCRM implementation that avoids this timeout:
https://github.com/civicrm/civicrm-core/compare/master...johanv:timeout_fix_update_relationship_status?expand=1

Instead of updating the records one by one, I now update all the records using an update statement.

I wonder whether I should create a pull request. Is there a particular reason for updating the relationships one by one?