[request/session] refactor language handling: don't attempt to sync web/repo languages This decouple thing and make code easier to understand. Previous behaviour was fine w/ validation error that were translated on the server side, but isn't satisfying for notification and all. Now: * translations should be done on the ui side (see previous validation error refactoring) * consistent behaviour: each side (web/repo) is responsible to deal with its request/session of language, no weird interaction between them on this topic * drop on the way the 'session properties' api, used only for that matter. -> much simpler/cleaner/saner api The thing missing being a way for user to tell "My favorite language is xxx but I also want cw to consider my http language header)

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