not at all - you just need (at the moment) to configure DB support in
openserctl (just do DBENGINE="MYSQL"). This does not require any
installation or what ever ...it just forces the inclusion of the file
with DB definition.
probably moving the def of this table to a not-DB related location will
be a good fix.
regards,
bogdan
Klaus Darilion wrote:
Thus, people which have not installed any DB module can use the lookup?
regards
klaus
Bogdan-Andrei Iancu wrote:
well... :)....even if it is a operation bouncing to cache (with no DB
implication), you need to know the name of location table, to be able
to search through cache....Like: search in "location" array for the
"xxx" AOR...
and the name of the location table is defined in the SQL section of
openserctl .....as it is related to DB...
in this case, it is not possible to do a strict separation between DB
and cache as the cache follows the structure and naming of the DB...
regards,
bogdan
Klaus Darilion wrote:
Bogdan-Andrei Iancu wrote:
Klaus,
it looks like the openserctl is not sending both parameter for the
MI call - the table name and the AOR. It should be like:
0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val <location>
0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val
<[EMAIL PROTECTED]>
0(5292) DEBUG:mi_fifo:mi_parse_tree: end of input tree
0(5292) DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
export DBENGINE="MYSQL" before running openserctl....if I'm not
wrong, the name of the location table is defined in the DB section
of openserctl.....so you need to use a DB engine ....
Although the communication between openserctl and openser is via
FIFO I have to define the DBENGINE? Why? I would the dumping the
location table should be done from cache thus not needing and DB
operation.
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
