[asterisk-dev] MySQL vs MariaDB
bferrell at baywinds.org
Thu Jan 24 13:46:56 CST 2013
On 01/24/2013 07:00 AM, jon pounder wrote:
> On 01/24/2013 09:53 AM, Matthew Jordan wrote:
> I completely support the ODBC approach (my company was involved with odbc when it was first ported to non-windows by Peter Harvey). I really don't understand why more projects
> don't implement the dbms this way since really its not any more work and its much more bang for the buck what you end up with.
> That said, if MariaDB is a drop in replacement it should work with the mysql odbc driver too since that's just a socket connection to the db from the driver.
> So bottom line odbc support should be all you need.
>> On 01/24/2013 08:05 AM, Bruce Ferrell wrote:
>>> On 01/24/2013 05:54 AM, Jared Smith wrote:
>>>> On Thu, Jan 24, 2013 at 8:47 AM, Bruce Ferrell <bferrell at baywinds.org>
>>>>> With various distros either moving to or considering a move to
>>>>> MariaDB, are
>>>>> there thoughts on Asterisk compatibility with MariaDB?
>>>>> I'm almost certain some will say that ODBC renders the issue moot,
>>>>> but I'm
>>>>> not so certain about that.
>>>> Maybe I'm not up to speed on MariaDB as much as I should be, but it's
>>>> my understanding that MariaDB is a drop-in replacement for MySQL --
>>>> same ABI, same data directory, and so forth. Am I mistaken?
>>> It's supposed to be. It's on my agenda to attempt in the next week or
>>> so and see what happens. Just wondering what thought(s) might be put
>>> into this and what I may need to know to get it to build
>> The current MySQL integration modules in Asterisk are, unfortunately,
>> relatively unsupported by the community. There have been discussions
>> about this in the past (originated by a discussion regarding the
>> deprecation of said modules - see ), but to date there hasn't been a
>> lot of movement on those issues . This may be because developers
>> haven't personally run into the issue; the issue is complex and hard to
>> reproduce (there's at least one memory corruption in the mix); or no one
>> feels like supporting them any longer. This is not an indictment or a
>> means to cast blame; it's just the reality of the situation.
>> As Tilghman and others have noted, focusing efforts on supporting the
>> ODBC modules means that we can provide reliable database integration
>> that works (generally) with everything. This gives us the most bang for
>> the buck, and keeps us from attempting to support everyone and actually
>> supporting no one.
>> Now, if someone would like to (a) write drivers to support MariaDB
>> (which may be just improving on the existing MySQL ones), (b) fix the
>> issues in the existing MySQL drivers (if necessary), and (c) commit to
>> being the module maintainer for said modules, I'd be happy to see them
>> in Asterisk.
>>  http://lists.digium.com/pipermail/asterisk-dev/2012-July/055988.html
>>  To see the bugs, run the following query in Jira: project=ASTERISK
>> and component in ("Addons/app_mysql", "Addons/cdr_mysql",
>> "Addons/res_config_mysql") and status=Open
Well, I'm just a guy who "hacks" dialplans... The ODBC approach doesn't *seem* quite as flexible to me or as easy to set up... But maybe that's just been the examples I've seen.
The bugs I see in JIRA look... Interesting. Not issues I've seen. I tend to use MySQL realtime and the MySQL app to perform queries that return values into my dialplan. ODBC
works well for the realtime part and doesn't seem to works as easily for the external queries... Again, maybe I just need education.
More information about the asterisk-dev