From 631c6a9a7471c7b6f3f74c0b7ab63ff109145546 Mon Sep 17 00:00:00 2001 From: Terry Wilson Date: Thu, 13 Oct 2011 00:05:17 +0000 Subject: [PATCH] Don't skip the query field on a realtime multi query There is no documented reason to not add the query field to the varlist returned by a realtime multi query, despite the config category being set to its value. Of course, there is no documentation that the category should be set to the value either. There is lots of no documentation when it comes to realtime. But, other engines do not skip this field so I am forcing this backend to follow the convention, because not doing so is very silly. git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.8@340662 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- res/res_config_sqlite.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/res/res_config_sqlite.c b/res/res_config_sqlite.c index fbeeac2750..b5b8de4ed0 100644 --- a/res/res_config_sqlite.c +++ b/res/res_config_sqlite.c @@ -1154,8 +1154,9 @@ static int add_rt_multi_cfg_entry(void *arg, int argc, char **argv, char **colum ast_category_append(args->cfg, cat); for (i = 0; i < argc; i++) { - if (!argv[i] || !strcmp(args->initfield, columnNames[i])) + if (!argv[i]) { continue; + } if (!(var = ast_variable_new(columnNames[i], argv[i], ""))) { ast_log(LOG_WARNING, "Unable to allocate variable\n");