Re: Does DLR have postgreSQL support?

Rory Campbell-Lange <rory 'at' campbell-lange.net> writes:

> I use a modified libsdb version that does not delete records once the
> dlr comes in.
> 
> It works ok, but we have only a few hundreds/thousands of messages a
> day. For each DLR call a new database connection is created, which is
> very inefficient.

This has been "fixed" in libsdb.

http://siag.nu/libsdb/news-0.5.3.shtml

Get the change, it's small (get the 0.5.2 -> 0.5.4 diff btw,
0.5.3 had a brown paper bag bug included).

You may also want to take the kannel changes for dbpool support.
 
> Really, the best way of using postgres would be to use the new sqlbox
> and instead of having a standard sql statement, use a postgres stored
> procedure with some custom triggers in the database. As you probably
> know, query plans for stored procedures are cached, so they are very
> very fast.

A native driver, that is (don't know exactly what's the diff
between standard kannel and sqlbox).

By the way, if stored procedures are that marvellous, why this
isn't used for the mysql native dlr implementation? as it seems
the vast majority of kannel users use mysql.

-- 
Guillaume Cottenceau