This module provides a DB APIv1 connector for the Redis server (https://www.redis.io). It can be used as a replacement for other database modules such as db_mysql and db_postgres. Not all the specs of DB APIv1 are implemented, thus the usage of this module might be restricted to specific modules. Also, for proper performance, this module needs particular configuration tailored to the modules that make use of it. Since Redis does not provide a schema by itself, db_redis ships with schema files. The path to these has to be defined using the module parameter "schema_path". The schema definition is defined in one file per table, such that the file name corresponds to the table name, and each file is composed of a comma-separated list of column definitions in the format <column-name>/<type>[,<column-name>/<type> ...] in one line, followed by a line holding the table version. Example definition for the "location" table (from the usrloc module): username/string,domain/string,contact/string,received/string,path/string,expires /timestamp,q/double,callid/string,cseq/int,last_modified/timestamp,flags/int,cfl ags/int,user_agent/string,socket/string,methods/int,ruid/string,reg_id/int,insta nce/string,server_id/int,connection_id/int,keepalive/int,partition/int 8 Because Redis is a key-value store, it requires unique keys. This means that tables and rows from a relational SQL database, e.g. from MySQL, can not be ported one a 1:1 basis to Redis. For instance, usrloc relies on a key of "user
Copyright © 2018 sipwise.com
