Hi Juha,
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...
Kind regards,
Carsten
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 transaction.
> + Locking only the "current" table causes problems with a MySQL-Databases
> + 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@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev