From 110c79d194c75c7ecb3afca2694320a8535872a7 Mon Sep 17 00:00:00 2001 From: Tilghman Lesher Date: Mon, 16 Feb 2009 17:07:57 +0000 Subject: [PATCH] Eliminate mention of a variable which exists only in trunk. (Thanks, jsmith) git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.1@176099 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/func_odbc.conf.sample | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/configs/func_odbc.conf.sample b/configs/func_odbc.conf.sample index 876416b07b..de8bbf37ca 100644 --- a/configs/func_odbc.conf.sample +++ b/configs/func_odbc.conf.sample @@ -49,12 +49,10 @@ ; changes the way that func_odbc normally works. Instead of the ; invocation of the function returning a row, it returns an opaque ; ID, which may be passed to ODBC_FETCH() to return each row in -; turn. ODBC_FETCH_STATUS returns SUCCESS or FAILURE, to indicate -; whether any results were stored, and you should call ODBC_Finish -; on the ID to clean up any remaining results when you are done -; with the query. Also, the variable ODBCROWS is set initially, -; which may be used in an iterative fashion to return each row in -; the result. +; turn. The variable ODBCROWS is set initially, which may be used +; in an iterative fashion to return each row in the result. You +; should call ODBC_Finish on the ID to clean up any remaining +; results when you are done with the query. ; Please note that multirow queries are isolated to the channel, ; and rows may not be fetched outside of the channel where the ; query was initially performed. Additionally, as the results are