On 20/09/10 16:17, Michael Scheidell wrote:
On 9/20/10 8:15 AM, Steve Freegard wrote:
Caching; if desired it will now cache URLs to a SQLite database for
additional speed-up and to prevent DoS of the shortener services.
any anticipated write lock problems with this due to sqlite not handling
multi-threaded reads/writes?
No; the module handles locking just fine. If you get two writes at
once; the first will block until the other completes. Being as this is
a very simple database this is unlikely to cause any problems.
Also; if you're really concerned about this or have reason to believe
you'll have high enough concurrency on the local machine for this to be
a problem, then see http://www.sqlite.org/wal.html which is new in
SQLite 3.7.
most (many?) SA installs already have db4. I guess maybe, hey, its open
source, get out your flowchart guys and write the db4 module :-)
I didn't use db4 as I'm not familiar enough with it. I also needed more
than just a key->value store to handle the expiry of old data
efficiently using indexed deletes and I've no idea how to do that in
db4. So patches welcome if someone really wants this.
Regards,
Steve.
