person collections in API late evaluate PersonTransferJob

[Robert Collins]

No timeouts yet, but its just a matter of time.
----------------------------------------------------------------------
SELECT 1 FROM (SELECT PersonTransferJob.json_data, PersonTransferJob.id, PersonTransferJob.job, PersonTransferJob.job_type, PersonTransferJob.major_person, PersonTransferJob.minor_person FROM Job, PersonTransferJob WHERE
                  PersonTransferJob.job_type = 1 AND PersonTransferJob.job = Job.id AND Job.status IN (0, 1, 4) AND (PersonTransferJob.minor_person = 251673 OR PersonTransferJob.major_person = 251673) LIMIT 1) AS "_tmp" LIMIT 1
----------------------------------------------------------------------
SELECT 1 FROM (SELECT PersonTransferJob.json_data, PersonTransferJob.id, PersonTransferJob.job, PersonTransferJob.job_type, PersonTransferJob.major_person, PersonTransferJob.minor_person FROM Job, PersonTransferJob WHERE
                  PersonTransferJob.job_type = 1 AND PersonTransferJob.job = Job.id AND Job.status IN (0, 1, 4) AND (PersonTransferJob.minor_person = 251672 OR PersonTransferJob.major_person = 251672) LIMIT 1) AS "_tmp" LIMIT 1

To see the behaviour:
bin/harness
team = factory.makeTeam(members=[factory.makePerson() for _ in range(100)])
print team
transaction.commit()
 run 'make run LP_DEBUG_SQL=1' visit api.launchpad.dev/1.0/~TEAMNAME/participants ?ws.size=75

[Robert Collins (lifeless)]

Also, I have to wonder why this is being looked up. having the job in the API seems uninteresting.

[Gavin Panella (allenap)]

It's probably being queried to populate the Person.is_merge_pending property. The easiest fix would be to stop exporting this property via the web-service API, or changing it to a function. It's relatively new so we don't need to keep it around for the sake of the 1.0 API.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r15578 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/15578>.