On Thu, Mar 13, 2008 at 9:17 AM, Andre Courchesne - Consultant
<[EMAIL PROTECTED]> wrote:
>   I was wondering is any of you have experience regarding the use of the
>  AstDB compared to a MySQL database queried via a php/perl script spawn
>  from AGI in the dialplan.
>
>   Right now my code uses AGI to spawn a php or perl script to keep track
>  of simple flags in an MySQL table. This leads sometimes to problems
>  (DeadAGi vs AGI,...)

First... skip using AGI for DB connectivity as it is unnecessary with
the advent of func_odbc. If you're just using DB access from the
dialplan (which seems to be the case if you're using an AGI()), then
func_odbc is going to be MUCH less overhead. See TFoTv2 [1] for
examples in chapter 12 of how to use func_odbc, including setting it
up (for PostgreSQL, but the solution is very similar for MySQL).

>   Driving in the car this morning I thought, well, why don't I use
>  AstDB? I only have around 700 entried in the table that I need to
>  query/update the value of.
>
>   Now, I do have external of asterisk scripts (cron, web,...) that will
>  need to query those flags also, but the AstDB is a DB2 database right so
>  I should be able to do that directly on the AstDB file from php/perl
>  right? Worst case I could use the manager interface.

Isn't it version 1 of the Berkley DB? It's a very simple family/key
system, which might work for your system, but if you've already gotten
the DB stuff ready to go, I'd encourage you to try func_odbc.

[1] -- http://downloads.oreilly.com/books/9780596510480.pdf

-- 
Leif Madsen.
http://www.leifmadsen.com
http://www.oreilly.com/catalog/asterisk

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to