<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">I agree, this should be a simple way to get it going, and though it would likely result in code duplication it could eventually require settings specific to MariaDB (though as Tim mentioned it’s essentially
a drop in replacement).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Kai, if you want to make a fork and then submit a pull request, I’m more than happy to test and add this to a new release. One thing that would be beneficial is if you can get some basic tests running for
it; IIRC this is a bit hacked in for the various DBI plugin modules.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">chris<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Bioperl-l <bioperl-l-bounces@bioperl.org> on behalf of Timothy Parnell <timothy.parnell@hci.utah.edu><br>
<b>Date: </b>Tuesday, September 3, 2024 at 12:19</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="font-size:12.0pt;color:black">PM<br>
<b>To: </b>bioperl-l@bioperl.org <bioperl-l@bioperl.org><br>
<b>Subject: </b>Re: [Bioperl-l] Support for MariaDB in Bio::DB:SeqFeature:Store::DBI::<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Regarding support for DBD::MariaDB, here is one (naive), hack solution: Simply copy the Bio/DB/SeqFeature/DBI/mysql.pm file as mariadb.pm, and search and replace “MySQL” with “MariaDB” as appropriate (watch
capitalization, etc). Since MariaDB is (more or less) a drop-in replacement for MySQL, in theory this should work just fine. If I remember correctly, the SQL commands and structures are not terribly complicated and fairly standard, so I wouldn’t expect much
more modification. If it does work, it might be worth a pull request.<br>
<br>
Tim<br>
<br>
_______________________________________________<br>
Bioperl-l mailing list<br>
Bioperl-l@bioperl.org<br>
<a href="https://urldefense.com/v3/__https:/mailman.open-bio.org/mailman/listinfo/bioperl-l__;!!DZ3fjg!6UzjoYFBT-qupAoTKJSjDhDnzGPDtnjbpi7RwrAfMEp3vRsAu1t7n3txH3-GPeS-GLzAXmmKUM3-Mukaza218K2MedsdUoU6Vfw$">https://urldefense.com/v3/__https://mailman.open-bio.org/mailman/listinfo/bioperl-l__;!!DZ3fjg!6UzjoYFBT-qupAoTKJSjDhDnzGPDtnjbpi7RwrAfMEp3vRsAu1t7n3txH3-GPeS-GLzAXmmKUM3-Mukaza218K2MedsdUoU6Vfw$</a>
<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>