[OpenSER-Devel] Change Storage Engine of OpenSER MySQL Database

[Sergio Gutierrez]

Hi Ovidiu.

Thanks for your feedback.

I implemented the feature in a per module group basis. At time to create the
groups of tables it asks whether the tables should be created as InnoDB, or
as MyISAM.

So, do you think is this approach right, or should it be implemented in a
global way for the whole tables?

Thanks.

Sergio

On Jan 9, 2008 2:26 PM, Ovidiu Sas <osas at voipembedded.com> wrote:

> Hi Sergio,
>
> I would suggest to make it configurable via a parameter inside the
> openserctlrc file.  Like this, at install time, users can choose which
> storage engine do they prefer for MySQL.  As a result, the install
> procedure will be backward compatible and a new feature will be added.
>
>
> Regards,
> Ovidiu Sas
>
> On Jan 9, 2008 1:40 PM, Sergio Gutierrez <saguti at gmail.com> wrote:
> > Hello everybody.
> >
> > A couple weeks ago, I published a Feature Request at OpenSER tracker,
> but I
> > am thinking I forgot to announce it at mail list.
> >
> > I proposed to change the storage engine for OpenSER tables in MySQL from
> its
> > default (MyISAM) to InnoDB. That storage engine offers several
> advantages
> > related to performance and scalability, and I think that for the
> behaviour
> > would expose a typical openser database, InnoDB would fit better than
> MyISAM
> >
> > The feature request is the 1851484, and it includes patches to modify
> the
> > scripts which create the tables in database;
> >
> > Please let me know what do you think about this feature. I would thank
> any
> > feedback; this is my first contribution to OpenSER.
> >
> > Best regards.
> >
> > Sergio Gutiérrez
> > EPM Telecomunicaciones S.A. E.S.P.
> > Medellin, Colombia.
> >
> >
> > _______________________________________________
> > Devel mailing list
> > Devel at lists.openser.org
> > http://lists.openser.org/cgi-bin/mailman/listinfo/devel
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openser.org/pipermail/devel/attachments/20080109/1255b204/attachment.htm