1.1. Design of dbtext engine 1.2. Internal format of a dbtext table The module implements a simplified database engine based on text files. It can be used by Kamailio DB interface instead of other database module (like MySQL). The module is meant for use in demos or small devices that do not support other DB modules. It keeps everything in memory and if you deal with large amount of data you may run out of memory quickly. Also, it does not implement all standard database facilities (like order by), it includes minimal functionality to work properly (who knows ?!?) with Kamailio. NOTE: the timestamp is printed in an integer value from time_t structure. If you use it in a system that cannot do this conversion, it will fail (support for such situation is in to-do list). NOTE: even when db_text is in non-caching mode, the module does not write back to hard drive after changes. In this mode, the module checks if the corresponding file on disk has changed, and reloads it. The write to disk happens at Kamailio shut down. If db_text is in caching mode, many "reload" functions in various modules will not work. 1.1. Design of dbtext engine The dbtext database system architecture: * A database is represented by a directory in the local file system. NOTE: when you use dbtext in Kamailio, the database URL for modules must be the path to the directory where the table-files are located, prefixed by “text://”, e.g., “text:///var/dbtext/ser”. If there is no “/” after “text://” then “CFG_DIR/”
Copyright © 2003, 2004 FhG FOKUS
