Re: [sr-dev] DB_ONLY mode in presence module

I’ve been looking through the presence module and have some questions regarding the DB_ONLY mode of operation. Specifically the feature seems to rely on data not being written to hash tables in certain areas of the code, as no checking is done to verify which db_mode is being used. However there are places where the hash table is populated irrelevant of the db_mode, for example the init code calls pres_htable_restore. Additionally update_presentity seems to also manipulate the hash tables indiscriminately. Am I missing something here, or is this a bug?