asterisk users - Oct 2003 - DB virtualization for multiple database support - Was Re: How to use vmdb.sql in voicemail.conf/extension.conf

> > 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20031005/831bade5/attachment.htm

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.

What about libdbi?  It already has the "pluggable" driver system, so 
thats half the work done already.
Its also licensed under the LGPL instead of the GPL, which if I have 
understood the discussions about
the GPL issues, should resolve problems of linking to that code.

Support for sqlite is cool too, since it saves running a database server 
for small setups that don't want
the extra (albeit small) overhead.

It would also be great if it is structured so that other
"vitualization"
interfaces can be written, to
provide the same sort of functionality for other parts of Asterisk.


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.

I think ODBC is the way to go.  There is really nothing to write.

> > 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.


====Chris Albertson
  Home:   310-376-1029  chrisalbertson90278@yahoo.com
  Cell:   310-990-7550
  Office: 310-336-5189  Christopher.J.Albertson@aero.org
  KG6OMK

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com