[sr-dev] git:4.1: presence: bugfix: Add option to disable per-Table lock for database layer
carsten at ng-voice.com
Sat Feb 1 22:53:01 CET 2014
all i can say is, that the locks make the presence module completely
unusable with a MySQL backend in DB_ONLY mode. The current database layer
will only lock the current table for a transaction, not all tables used
during one transaction. And that results in an unusable database connection.
In order to change that, i'd have to the complete database API. ..
The RLS-Module has a similar option already...
Am 01.02.2014 20:38 schrieb "Juha Heinanen" <jh at tutpro.com>:
> Carsten Bock writes:
> > presence: bugfix: Add option to disable per-Table lock for database layer
> > (causes trouble with MySQL in DB_ONLY mode)
> > + <title><varname>db_table_lock_type</varname> (integer)</title>
> > + <para>
> > + Enable (=1) or disable (=0) the Locks for table during an
> > + Locking only the "current" table causes problems with a
> > + in "DB-Only" mode.
> does it make sense to disable the locks? i would imagine that they were
> introduced for a purpose. what can break if locks are not used?
> does the same MySQL trouble exist with locks used in rls module?
> -- juha
> sr-dev mailing list
> sr-dev at lists.sip-router.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sr-dev