<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Lucida Console'; font-size:9pt; font-weight:400; font-style:normal;">On Freitag, 9. Oktober 2009, Juha Heinanen wrote:<br>
> > I agree. IMHO both kamctl and kamdbctl tools can be promoted as new<br>
> > management scripts for sip-router.<br>
><br>
> regarding kamctl, i don't think that it is a good idea to include<br>
> possibility to provision database table entries with it. lcr, for<br>
> example, has a large number of fields in gw table and it is very<br>
> cumbersome to try to add gws using kamctl. phpmyadmin, siremis,<br>
> etc. are much better tools for that.<br>
><br>
> so my suggestion is to drop all db record related operations from<br>
> kamctl.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I also think that the scripts are a bit cumbersome, i never used kamctl for DB provisioning sof far. But aparently some people uses this, as i received a bunch of patches for adding support for cr tables for example, or to fix problems in existing ctl code in the past. So i don't think we should remove it right now. Before that we should add a "this is obselete and its planned to be removed, please speak up now" warning message to the script and let it stay there for one release cycle.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Regards,<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Henning</p></body></html>