Re: dlr_sdb bug
Stipe Tolj <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Organization | Wapme Systems AG |
| Message-ID | <[email protected]> |
> that was a reason why I added sdb_get_limit_str(), so if db support another > limit clause (as oracle ROWNUM) then you can just add it there... Using > libsdb is anyway a bad idea, because libsdb doesn't support persistent db > connections. And from my experience, I know that opening a db connection take > more time as sql statement itself. yep, this should be stated as notice into the user's guide. Using libsdb as a DLR repository should be the first try or low throughput solution. When facing a high-load system, then users should move to an other option, mainly Oracle or MySQL. SQLite may also me an alternative. I have the dbpool already for this, but yet not the DLR stuff. > Heh, in order to find this unique key you must make select statement anyway. > Later if you have found a appropriate row, yes we should do it. But if you > speek about performance, then first what we should do (imo): get rid of > libsdb support and add native db support for db's we want... Rory, this is valid in case you have several msg/sec. on traffic. Anyway Rory uses PostgreSQL, and we don't have native support for it. Stipe [email protected] ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [email protected] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are