fix optimisation with super session that may lead to integrity loss at some point I've decided to stop ensuring ?1 cardinality was respected when adding a new relation using a super session, to avoid the cost of the delete query. That was yet discussable because it introduced unexpected difference between execute and unsafe_execute, which is imo not worth it. Also, now that rql() in migration script default to unsafe_execute, we definitly don't want that implicit behaviour change (which already cause bug when for instance adding another default workflow for an entity type: without that fix we end up with *two* default workflows while the schema tells we can have only one. IMO we should go to the direction that super session skip all security check, but nothing else, unless explicitly asked.

     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 ;;