author | Florian Forster <octo@leeloo.lan.home.verplant.org> | |
Tue, 17 Mar 2009 13:30:02 +0000 (14:30 +0100) | ||
committer | Florian Forster <octo@leeloo.lan.home.verplant.org> | |
Tue, 17 Mar 2009 13:30:02 +0000 (14:30 +0100) | ||
commit | 6eafacc52a73444fa23510fc838cd9658dc6844c | |
tree | 59e9ded61856cb08a978cba6ab4dab17884ea862 | tree | snapshot |
parent | 52d812cb04c4d9746c7a6520a0c0272fbce5d296 | commit | diff |
mysql plugin: Some changes to the configuration handling.
The member `instance' is used to determine whether or not to use ``legacy
mode'':
- If it is NULL, legacy mode is in action
- Otherwise, non-legacy mode should be used.
``legacy mode'' and ``non-legacy mode'' cannot be mixed: If at least one
database is defined in the ``new'' way, all options that'd be valid in
legacy mode will only trigger a warning.
The member `instance' is used to determine whether or not to use ``legacy
mode'':
- If it is NULL, legacy mode is in action
- Otherwise, non-legacy mode should be used.
``legacy mode'' and ``non-legacy mode'' cannot be mixed: If at least one
database is defined in the ``new'' way, all options that'd be valid in
legacy mode will only trigger a warning.
src/mysql.c | diff | blob | history |