[Asterisk-Dev] RE: MYSQL application

John Turner jdturner at nc.rr.com
Mon Aug 2 20:22:49 MST 2004


On Aug 2, 2004, at 9:46 PM, Kevin Walsh wrote:

> Constantine Filin [cfilin at intermedia.net] wrote:
>>> While I understand the concern of too many 'vendor' specific
>>> implementations, I applaud the inclusion of 'query', 'insert', etc.
>>> commands into the asterisk dialplan versus through an AGI.  If the
>>> general consensus is to move this into ast_data, then that is good as
>>> well, as long as the more useful database functions are not lost in 
>>> the
>>> process.
>>>
>> There is no problem if MYSQL is not included in CVS, still I thought 
>> if
>> this work well for me, then it might work for someone else as well.
>>
>> On the subject of developing a single interface to all database from *
>> dialplans - what about unix ODBC and commands like
>> 	ODBC(Connect DSN connID ...)
>> 	ODBC(Query ${connID} resultID ...)
>> 	ODBC(Fetch ${resultID} fetchID...)
>> 	ODBC(Disconnect ${connID} ...)
>> 	ODBC(Clear${resultID}
>> would they be generic enough?
>>
> ODBC is horribly inefficient.  I wouldn't go near it.  Perhaps a
> more generic interface would be better.  Something like the
> following:
>

Why not something like Perl DBI?  Here is a C library that could be 
used as the backend.

http://libdbi.sourceforge.net/

John




More information about the asterisk-dev mailing list