aboutsummaryrefslogtreecommitdiffstats
path: root/configs/func_odbc.conf.sample
diff options
context:
space:
mode:
Diffstat (limited to 'configs/func_odbc.conf.sample')
-rw-r--r--configs/func_odbc.conf.sample10
1 files changed, 4 insertions, 6 deletions
diff --git a/configs/func_odbc.conf.sample b/configs/func_odbc.conf.sample
index 876416b07..de8bbf37c 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