<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii">
<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">As a suggestion for 5.0 having a scripted DB migration system would make upgrading much easier.<o:p></o:p></p>
<p class="MsoNormal">Something like what Asterisk now uses (Alembic https://pypi.python.org/pypi/alembic) would be ideal, as it works in a DB agnostic manner and you would just have to ensure that there is a driver for the DB you wish to use.<o:p></o:p></p>
<p class="MsoNormal">That way you would just update the definition script and select the target when you run the updater, and would allow kamailio a greater choice in backing DB’s as once the script is written assuming a driver is available for you RDBMS the
schema would be successfully ported.<o:p></o:p></p>
<p class="MsoNormal">This would do away with maintaining separate MySQL, Postgres, Oracle, MSSQL scripts as well.<o:p></o:p></p>
<p class="MsoNormal">The only issue I can think with a system like this is in the situation where hardcoded SQL strings are in the source and use a RDBMS specific function as that could cause some “fun” in debugging…<o:p></o:p></p>
</div>
</body>
</html>