Instead of ejabberd.sql , I use a custom MySQL schema (due to legacy reasons).
I will perform some operations with the database on some actions, such as Ping, Pong, Msg deliverd, Msg read and, most importantly, get / set the list of the list and declare the presence (all this on my own scheme).
However, ejabberd seems to use ejabberd.sql everywhere, and its source code is heavily dependent on it. Using source code is the last thing I would do, since I don't know its dependencies.
Possible ideas:
Let's say if I extend ejabberd by writing my own modules, then what use will be mod_roster_odbc? I just do not want to lose all the functionality of ejabberd, but I have no choice but to use a special scheme here.
OR
Do I need to modify every request in odbc_queries and ejabberd_odbc . If there is a certain centralized module that allows me to modify requests, reflecting it everywhere, without breaking the harmony of ejabberd, that would be great.
In general, I want to avoid dependency problems and make my work as possible as possible. But I'm pretty vague about what a better approach might be?
source
share