Indeed, the docs are misleading. The test is on advertised async insert in db driver and if yes, it is used. If async workers is not set, then nothing happens in this case (I added a warning in the code for this case).
Sync insert is done if async insert is wanted but not available in the db driver and this is done in the acc module.
This needs to be fixed to match the docs, but I am not sure where it would a better place, inside acc (test if async workers is not set and do db sync insert, so a solution specific for acc) or do it inside db mysql async insert function (a global behaviour across modules when db mysql is used) ... any preference by people here?
Cheers, Daniel
On 08.11.17 12:19, Juha Heinanen wrote:
Found the reason why db acc had stopped working: I had removed async_workers parameter. Looks like acc module does not insert anything if db_insert_mode=2 and there is no async workers. From README, I get the impression that it should be doing standard insert in that case:
6.28. db_insert_mode (integer)
If set to 2, async insert is used if the db driver module has support for it and if async_workers core parameter value is greater than 0. If not, then standard INSERT is used.
-- Juha
Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev