jambonz / db-helpers Goto Github PK

When this feature is installed, the existing rows in the table will have NULL for last_updated. The sql statement:

should clean BOTH rows which have a NULL last_updated as well as those that have a last_updated value older than the interval

As of release 0.8.3 the sbc_addresses table also includes optional columns for tls_port and wss_port, in addition to the 'port' column which has always kept the udp port. The api should be updated to allow these new columns to be populated as well. This will be optional as not every system will necessarily be listening for tls and wss.

It would be nice to give customers a choice of postgresql or mysql for the jambonz provisioning database. This would mean changes here but also in feature server and some other apps

Currently both read and write transactions are written to the single database specified by the JAMBONES_MYSQL_XXX environment variables. I would like to add an additional set of env vars:

JAMBONES_MYSQL_WRITE_HOST
JAMBONES_MYSQL_WRITE_PORT
JAMBONES_MYSQL_WRITE_USER
JAMBONES_MYSQL_WRITE_PASSWORD
JAMBONES_MYSQL_WRITE_DATABASE
JAMBONES_MYSQL_WRITE_CONNECTION_LIMIT

These are optional and if not provided then the behavior is as current. However, for an installation that wishes to send all write transactions (e.g. INSERT, UPDATE, or DELETE) to a centralized master database, but read against a local readonly slave, they would provide values for the JAMBONES_MYSQL_WRITE_XXX env vars in addition to the JAMBONES_MYSQL_XXX which are still required.

It is possible to call pp.query with an object, rather than array, e.g.

[
   {
       sql: 'SELECT * \nFROM accounts account \nWHERE account.account_sid = ?',
       nestTables: true
    },
    '9351f46a-678c-43f5-b8a6-d4eb58d131af'
]

Statements like these will not be cached.