[asterisk-commits] tilghman: branch 1.6.0 r176098 - /branches/1.6.0/configs/func_odbc.conf.sample

[SVN commits to the Asterisk project]

Author: tilghman
Date: Mon Feb 16 11:06:39 2009
New Revision: 176098

URL: http://svn.digium.com/svn-view/asterisk?view=rev&rev=176098
Log:
Eliminate mention of a variable which is only available in trunk.

Modified:
    branches/1.6.0/configs/func_odbc.conf.sample

Modified: branches/1.6.0/configs/func_odbc.conf.sample
URL: http://svn.digium.com/svn-view/asterisk/branches/1.6.0/configs/func_odbc.conf.sample?view=diff&rev=176098&r1=176097&r2=176098
==============================================================================
--- branches/1.6.0/configs/func_odbc.conf.sample (original)
+++ branches/1.6.0/configs/func_odbc.conf.sample Mon Feb 16 11:06:39 2009
@@ -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