If you want to query data of just 50 participants, then this will take ~10 seconds which makes this API function unusable for medium size number of participants.

Trougakoss, do you have any idea why this is so slow?

Can this be fixed easily or should we better aim for an alternative solution which might be a new function returning all token entries with their related data so we can prevent using a loop with lots of single queries?

@Trougakoss, the user who has reported that problem is willed to donate to Limesurvey (or you) if this could be fixed soon.

If you think this is a no fix and should be solved by a new function, please let us know.

Thanks!

The first think that comes in mind is that we might enhance list_participants to provide with more data than just [tid,token,fistname,lastname,email] (language, remindersent, remindercount, completed, as long as it exists in the token table).

As for the speed of the get_participant_properties, you state that it takes 0.2 seconds, which is more or less the same as the list participants. If you accumulate the time for 50 queries, it is expected to take a long time. I do not think that it was intended to perform that many queries.

So i will look into enhancing list-participants, as soon as possible , if there is no better idea

Spiros, please close this ticket once the new function was added to the Limesurvey core.

Thanks for your great work!

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=12286

2.00+ Build 130424 release