improve massive deletion performance change hooks.integrity._DelayedDeleteOp implementation to give it a chance of processing the entities by chunks of reasonnable size (500 entities at a time) adapt ssplanner.DeleteEntitiesStep to call a variant of glob_delete_entity with several entities. That variant calls all the before_delete_entities hooks in one go, then performs the deletion, and then calls all the after_delete_entities hooks. The deletion is performed by grouping together entities by etype and by source. adapt the HooksManager to call the hooks on a list of entities instead of on a single entity. adapt the sources to be able to delete several entities of the same etype at once. changed the source fti_(un)index_entity methods to fti_(un)index_entities taking a collection of entities.

     1

/* -*- sql -*- 

     2

     3

   mysql specific registered procedures, 

     4

     5

*/

     6

     7

/* XXX limit_size version dealing with format as postgres version does.

     8

   XXX mysql doesn't support overloading, each function should have a different name

     9

    10

   NOTE: fulltext renamed since it cause a mysql name conflict

    11

 */

    12

    13

CREATE FUNCTION text_limit_size(vfulltext TEXT, maxsize INT)

    14

RETURNS TEXT

    15

NO SQL

    16

BEGIN

    17

    IF LENGTH(vfulltext) < maxsize THEN

    18

       RETURN vfulltext;

    19

    ELSE

    20

       RETURN SUBSTRING(vfulltext from 1 for maxsize) || '...';

    21

    END IF;

    22

END ;;