Screen plugin EPrint::Messages inefficient?

[tmb]

Effectively executes the following query everytime an EPrint::View screen is displayed:

SELECT DISTINCT T0.historyid FROM history T0 WHERE (T0.datasetid = 'eprint');

Although the query executes fairly quickly, for very large history datasets it can take a few seconds to read in the list of IDs returned and then merge them with the accumulated list of IDs..

EPrint::Messages::can_be_viewed calls get_messages which searches the history dataset.

[tmb]

Note - is a distinct needed here - historyid should always be unique?

[tmb]

Workaround:

Disable plugin altogether or remove the datasetid="eprint" condition from the search in EPrint::Messages::get_messages (and assume that mail_owner and note actions won't be carried out on other types of dataobj..)

[tmb]

Chris - does the reworked 3.2 search code still run 1+ queries per search condition and then merge the lists of IDs returned?

[tdb01r]

This is no longer applicable to 3.2.