Atis Lezdins wrote:
> On Mon, Nov 24, 2008 at 8:01 PM, Julian Lyndon-Smith <[EMAIL PROTECTED]>
> wrote:
>
>> For me, the "best" is the curl function, along with res_config_curl.
>> Best of all worlds - pass a web query to *whatever* backend system you
>> want to implement. No messy ODBC drivers
On Mon, Nov 24, 2008 at 8:01 PM, Julian Lyndon-Smith <[EMAIL PROTECTED]> wrote:
> For me, the "best" is the curl function, along with res_config_curl.
> Best of all worlds - pass a web query to *whatever* backend system you
> want to implement. No messy ODBC drivers.
>
> It's really, really good st
For me, the "best" is the curl function, along with res_config_curl.
Best of all worlds - pass a web query to *whatever* backend system you
want to implement. No messy ODBC drivers.
It's really, really good stuff ;)
Julian.
Jared Smith wrote:
> On Sun, 2008-11-23 at 00:47 -0500, Al Baker wrote
On Sun, 2008-11-23 at 00:47 -0500, Al Baker wrote:
> Quote "
> The preferred method is to use func_odbc, which takes SQL queries and
> builds custom dialplan functions from them. I've used it quite a bit,
>
> and am very happy with it."
>
> How can you be VERY HappY with something that allows O
On Sun, 2008-11-23 at 00:42 -0500, Al Baker wrote:
> func_odb only allows a SINGLE database statement
> Ergo you cannot do Transactions or Multi-statement
> SQL
It's my understanding that one of the Digium developers is working on
adding transaction support to func_odbc.
> Digium should support
Klaus Darilion wrote:
> Hi Jared!
>
> Thanks for the info - looks very flexible - you only have to edit 4
> configuration files for a simple query :-)
>
> just a few questions:
> The ODBC library is unixodbc?
>
> How does it compare to the other solutions in terms of performance? e.g.
> (I have
Klaus Darilion wrote:
> Wolfgang Pichler schrieb:
>
>> Hi,
>>
>> you yould also use DBQuery (does only support mysql) - take a look at
>> http://www.voip-info.org/wiki/view/Asterisk+cmd+DBQuery (it does also
>> contain a cdr backend to write customzied cdr entries to the database)
>>
>
>
Hi,
yes - i did have done it myself.
The main difference is that the dbquery application does use the
res_mysqlpool - which is a small piece of code which does handle a pool
of connections to one or more mysql servers. So you can make a fault
tolerant system by using two master - master replic
Hi Jared!
Thanks for the info - looks very flexible - you only have to edit 4
configuration files for a simple query :-)
just a few questions:
The ODBC library is unixodbc?
How does it compare to the other solutions in terms of performance? e.g.
(I have to make several queries for each call (c
Wolfgang Pichler schrieb:
> Hi,
>
> you yould also use DBQuery (does only support mysql) - take a look at
> http://www.voip-info.org/wiki/view/Asterisk+cmd+DBQuery (it does also
> contain a cdr backend to write customzied cdr entries to the database)
hi wolfgang!
Have you programmed this you
Hi,
you yould also use DBQuery (does only support mysql) - take a look at
http://www.voip-info.org/wiki/view/Asterisk+cmd+DBQuery (it does also
contain a cdr backend to write customzied cdr entries to the database)
regards,
Wolfgang
Klaus Darilion schrieb:
> Hi!
>
> What is the preferred way t
On Thu, 2008-11-13 at 15:16 +0100, Klaus Darilion wrote:
> What is the preferred way to make database lookups from within the dialplan?
The preferred method is to use func_odbc, which takes SQL queries and
builds custom dialplan functions from them. I've used it quite a bit,
and am very happy wit
Hi!
What is the preferred way to make database lookups from within the dialplan?
I only know the MYSQL function from asterisk-addons. Are the other
methods too? (e.g. for postgresql, unixodbc)
thanks
klaus
___
-- Bandwidth and Colocation Provided by
13 matches
Mail list logo
