Sobre MariaDB e o foco no ODBC...<div><br></div><div>Denis.<span></span><br><br>---------- Forwarded message ----------<br>From: <b>Matthew Jordan</b> <br>Date: Thursday, January 24, 2013<br>Subject: [asterisk-dev] MySQL vs MariaDB<br>
To: Asterisk Developers Mailing List <<a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a>><br><br><br>On 01/24/2013 08:05 AM, Bruce Ferrell wrote:<br>
> On 01/24/2013 05:54 AM, Jared Smith wrote:<br>
>> On Thu, Jan 24, 2013 at 8:47 AM, Bruce Ferrell <<a href="javascript:;" onclick="_e(event, 'cvml', 'bferrell@baywinds.org')">bferrell@baywinds.org</a>><br>
>> wrote:<br>
>>> With various distros either moving to or considering a move to<br>
>>> MariaDB, are<br>
>>> there thoughts on Asterisk compatibility with MariaDB?<br>
>>><br>
>>> I'm almost certain some will say that ODBC renders the issue moot,<br>
>>> but I'm<br>
>>> not so certain about that.<br>
>> Maybe I'm not up to speed on MariaDB as much as I should be, but it's<br>
>> my understanding that MariaDB is a drop-in replacement for MySQL --<br>
>> same ABI, same data directory, and so forth. Am I mistaken?<br>
> It's supposed to be. It's on my agenda to attempt in the next week or<br>
> so and see what happens. Just wondering what thought(s) might be put<br>
> into this and what I may need to know to get it to build<br>
><br>
<br>
The current MySQL integration modules in Asterisk are, unfortunately,<br>
relatively unsupported by the community. There have been discussions<br>
about this in the past (originated by a discussion regarding the<br>
deprecation of said modules - see [1]), but to date there hasn't been a<br>
lot of movement on those issues [2]. This may be because developers<br>
haven't personally run into the issue; the issue is complex and hard to<br>
reproduce (there's at least one memory corruption in the mix); or no one<br>
feels like supporting them any longer. This is not an indictment or a<br>
means to cast blame; it's just the reality of the situation.<br>
<br>
As Tilghman and others have noted, focusing efforts on supporting the<br>
ODBC modules means that we can provide reliable database integration<br>
that works (generally) with everything. This gives us the most bang for<br>
the buck, and keeps us from attempting to support everyone and actually<br>
supporting no one.<br>
<br>
Now, if someone would like to (a) write drivers to support MariaDB<br>
(which may be just improving on the existing MySQL ones), (b) fix the<br>
issues in the existing MySQL drivers (if necessary), and (c) commit to<br>
being the module maintainer for said modules, I'd be happy to see them<br>
in Asterisk.<br>
<br>
[1] <a href="http://lists.digium.com/pipermail/asterisk-dev/2012-July/055988.html" target="_blank">http://lists.digium.com/pipermail/asterisk-dev/2012-July/055988.html</a><br>
<br>
[2] To see the bugs, run the following query in Jira: project=ASTERISK<br>
and component in ("Addons/app_mysql", "Addons/cdr_mysql",<br>
"Addons/res_config_mysql") and status=Open<br>
<br>
Matt<br>
<br>
--<br>
Matthew Jordan<br>
Digium, Inc. | Engineering Manager<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA<br>
Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> & <a href="http://asterisk.org" target="_blank">http://asterisk.org</a><br>
<br>
<br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
<br></div>