<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">I'm getting into this a bit late so sorry if I'm repeating something already said.<br><br>It would be great to see an option for astdb to use an alternative DB other than the builtin BerkleyDB. What ever changes are made though should be transparent to current astdb calls so that we can make sure to preserve the eco-system that revolves around Asterisk. (Manager access to astdb today and AGI scripts - which is used by GUIs, XML scripts, apps like iSymphony, etc.)<br><br>Russel is correct that anyone who does not need anything special should not be impacted, things should just work.<br><br>What I have always envisioned, conceptually, is to modify the db.c code so that you could configure it to transparently use func_odbc.c under the covers, thus preserving everything including all internal Asterisk code and the rest of the eco system around Asterisk.<br><br>If
those are already implied in the previous discussion, then great. Otherwise...<br><br>Philippe Lindheimer<br>FreePBX Project Leader<br><br><br><br>--- On <b>Mon, 10/27/08, asterisk-dev-request@lists.digium.com <i><asterisk-dev-request@lists.digium.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">Date: Mon, 27 Oct 2008 09:53:12 -0700<br><pre>From: Russell Bryant <russell@digium.com><br>Subject: Re: [asterisk-dev] New license for db?<br>To: Asterisk Developers Mailing List <asterisk-dev@lists.digium.com><br>Message-ID: <514A4424-1DF2-4B21-80BE-6725A3973E23@digium.com><br>Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes<br><br><br>On Oct 27, 2008, at 4:07 AM, Sergey Tamkovich wrote:<br><br>> This won't be too hard, since realtime now supports store and destroy<br>> methods in addition to select and update,<br>> We could simplify code
base and give a choice to an end user if we'll<br>> change astdb with realtime subsystem.<br>> Maybe i'm missing some points here, but i like an idea of realtime<br>> instead of astdb very much.<br><br><br>It's certainly possible, but as it stands, it does introduce an <br>additional configuration burden on _every_ user of Asterisk. The nice <br>thing about astdb today is that it requires no additional <br>configuration. So for the minimal usage it gets inside the code, and <br>for very basic dialplan usage, it's ready to go without any extra <br>work. But, if you want anything more advanced, you have to set up <br>realtime or func_odbc.<br><br>--<br>Russell Bryant<br>Senior Software Engineer<br>Open Source Team Lead<br>Digium, Inc.<br><br><br><br><br><br><br><br>------------------------------<br><br>_______________________________________________<br>--Bandwidth and Colocation Provided by
http://www.api-digital.com--<br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> http://lists.digium.com/mailman/listinfo/asterisk-dev<br><br>End of asterisk-dev Digest, Vol 51, Issue 57<br>********************************************<br></pre></blockquote></td></tr></table><br>