Hi Daniel, Another option would be to enhance openserctl to use the SQL engine for DBENGINE=MYSQL and DBENGINE=PGSQL (as it is today), and create a DBTEXT engine for DBENGINE=DBTEXT (by incorporating sc.dbtext into openserctl). Like this, we will have a single script.
Regards, Ovidiu Sas On 2/5/07, Ovidiu Sas <[EMAIL PROTECTED]> wrote:
Hi Daniel, As long as it is there and I don't need to make custom builds, it works for me :) Maybe we can "standardize" DBTEXT as a value for DBENGINE (just like MYSQL and PGSQL). Cheers, Ovidiu On 2/5/07, Daniel-Constantin Mierla <[EMAIL PROTECTED]> wrote: > Hello Ovidiu, > > maybe the reference should be done in the openserctl help. Printing the > message all the time might become annoying. Another place is the readme > of dbtext module. > > The name might be better to have it as openserctl_dbtext -- for me > suggests move obvious that it is about openserctl, not openser. > > Cheers, > Daniel > > > On 02/01/07 18:40, Ovidiu Sas wrote: > > Hi, > > > > > > Since dbtext is part of the standard, my suggestion would be to > > ship/install the sc.dbtext script along with the openserctl script. > > > > We can install it as openser_dbtext_ctl and in openserctl we can make > > a reference to it if no DBENGINE is provided: > > > > see the following patch for openserct (openser-v1.1.1): > > diff -Naurp sip-server/scripts/openserctl openser/scripts/openserctl > > --- sip-server/scripts/openserctl 2006-09-15 08:41:42.000000000 > > -0400 > > +++ openser/scripts/openserctl 2007-01-17 09:39:09.000000000 -0500 > > @@ -126,6 +126,8 @@ do > > $f > > done > > echo > > + echo "Note: Use openser_dbtext_ctl for DBTEXT operations!" > > + echo > > > > } > > > > > > > > Regards, > > Ovidiu Sas > > > > _______________________________________________ > > Users mailing list > > [email protected] > > http://openser.org/cgi-bin/mailman/listinfo/users > > >
_______________________________________________ Users mailing list [email protected] http://openser.org/cgi-bin/mailman/listinfo/users
