Change hooks control (deny_all_hooks_but / allow_all_hooks_but) to be more predictable Prior to this, if one execute code like: with cnx.hooks.deny_all_hooks_but('metadata'): with cnx.hooks.deny_all_hooks_but(): # mycode 'metadata' hooks will be activated anyway in the inner block, which is rather unexpected (of course in real life you only see the latest hooks control statement, the former being higher in the call stack). This is due to the underlying usage of old `enable_hook_categories` / `disable_hook_categories` methods, which were introduced much before the now official context manager based API (with `cnx.[deny|all]_all_hooks_but(...)`). To move on, this patch drop the two legacy methods, rename and privatize related internal state on the connection (`hooks_mode` becomes `_hooks_mode`, `disabled_hook_cats` and `enabled_hook_cats` become `_hooks_categories`) and reimplement the `_hooks_control` context manager to simply update them. See the added unit test for details.

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