[Asterisk-Users] Re: DB virtualization for multiple database support - Was Re: [Asterisk-Users] How to use vmdb.sql in voicemail.conf/extension.conf

[Marcel Prisi]

If you write code in C/C++, you'd better use "sqlrelay" :

http://sqlrelay.sourceforge.net/

SQL Relay is a persistent database connection pooling, proxying and load 
balancing system for Unix and Linux supporting ODBC, Oracle, MySQL, 
mSQL, PostgreSQL, Sybase, MS SQL Server, IBM DB2, Interbase, Lago and 
SQLite with APIs for C, C++, Perl, Perl-DBI, Python, Python-DB, Zope, 
PHP, Ruby, Ruby-DBI, TCL and Java, command line clients, a GUI 
configuration tool and extensive documentation. The APIs support 
advanced database operations such as bind variables, multi-row fetches, 
client side result set caching and suspended transactions. It is ideal 
for speeding up database-driven web-based applications, accessing 
databases from unsupported platforms, migrating between databases, 
distributing access to replicated databases and throttling database access.

:-)

Garry Adkins wrote:
> Not familiar with it...  You have a URL?
> 
> 
> ----- Original Message ----- 
> From: "Matteo Brancaleoni" <mbrancaleoni at espia.it>
> To: <asterisk-users at lists.digium.com>
> Sent: Sunday, October 05, 2003 4:52 PM
> Subject: [Asterisk-Users] Re: DB virtualization for multiple database
> support - Was Re: [Asterisk-Users] How to use vmdb.sql in
> voicemail.conf/extension.conf
> 
> 
> 
>>Like what PEARS (php libs) do for db backends?
>>
>>Matteo.
>>
>>Garry Adkins wrote:
>>
>>> > > I am trying a scenerio where the * will take the email and mailbox
>>>number from the Mysql database for sendming mail to a voicemail user. I
>>>have seen vmdb.sql file but is not able to determine its use.
>>>
>>> > You can't anymore MySQL was ripped from Asterisk because the client
> 
> libs
> 
>>> > are GPL.
>>>
>>>I would be more than happy to help write a DB "Virtualization" function
>>>for *.
>>>
>>>I *love* the way it works in Java, but that's not a real possibility.
>>>It wouldn't need to be as complicated as JDBC but it's a nice model.
>>>
>>>We could however:
>>>1)  Abstract out the schema from the database calls
>>>2)  Develop a "pluggable" driver interface to translate to whatever DB
>>>you're using.
>>>
>>>This way...  You want MySQL, you develop a "translation driver" that
>>>maps * db calls to MySql.  (fairly trivial)
>>>Same for Postgres  (I'd suggest making this the default, as no GPL
>>>issues for mark, etc.)
>>>Same for Oracle, etc.
>>
>>
>>_______________________________________________
>>Asterisk-Users mailing list
>>Asterisk-Users at lists.digium.com
>>http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>>
> 
> 
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users