Well, the call to build_completion_hash() is optional. Whether it is called or not is determined by the startup options that are passed to drizzled.
The startup option that controls it is opt_rehash as you can see from this block:
if (opt_rehash)
com_rehash(NULL, NULL);
Looking at the description of this option, we see:
{"auto-rehash", OPT_AUTO_REHASH,
N_("Enable automatic rehashing. One doesn't need to use 'rehash' to get table and field completion, but startup and reconnecting may take a longer time. Disable with --disable-auto-rehash."),
(char**) &opt_rehash, (char**) &opt_rehash, 0, GET_BOOL, NO_ARG, 1, 0, 0, 0,
0, 0}
So if you pass the --disable-auto-rehash option to drizzled on startup, build_completion_hash() will not get called from the reconnect() method.
Well, the call to build_completio n_hash( ) is optional. Whether it is called or not is determined by the startup options that are passed to drizzled.
The startup option that controls it is opt_rehash as you can see from this block:
if (opt_rehash)
com_rehash(NULL, NULL);
Looking at the description of this option, we see:
{"auto-rehash", OPT_AUTO_REHASH, auto-rehash. "),
N_("Enable automatic rehashing. One doesn't need to use 'rehash' to get table and field completion, but startup and reconnecting may take a longer time. Disable with --disable-
(char**) &opt_rehash, (char**) &opt_rehash, 0, GET_BOOL, NO_ARG, 1, 0, 0, 0,
0, 0}
So if you pass the --disable- auto-rehash option to drizzled on startup, build_completio n_hash( ) will not get called from the reconnect() method.
-Padraig