From e9251f42df12ad38367f80265aea46f7d7a68875 Mon Sep 17 00:00:00 2001 From: Tilghman Lesher Date: Thu, 31 May 2007 15:05:56 +0000 Subject: Issue 9799 - Multirow results for func_odbc git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@66734 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/func_odbc.conf.sample | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'configs') diff --git a/configs/func_odbc.conf.sample b/configs/func_odbc.conf.sample index 2405952f8..ff9e1c17b 100644 --- a/configs/func_odbc.conf.sample +++ b/configs/func_odbc.conf.sample @@ -67,4 +67,11 @@ writesql=UPDATE presence SET location='${SQL_ESC(${VAL1})}' WHERE id='${SQL_ESC( ;escapecommas=no ; Normally, commas within a field are escaped such that each ; field may be separated into individual variables with ARRAY. ; This option turns that behavior off [default=yes]. +;mode=multirow ; Enable multirow fetching. Instead of returning results directly, + ; mode=multirow queries will return a result-id, which can be passed + ; multiple times to ODBC_FETCH, and that function will return each + ; row, in order. You can add to this the following parameter: +;rowlimit=5 ; rowlimit will limit the number of rows retrieved and stored from + ; the database. If not specified, all rows, up to available memory, + ; will be retrieved and stored. -- cgit v1.2.3