> In defence of SQLite (not that I'm especially cheering for it), it > actually is ACID compliant (http://www.sqlite.org/transactional.html, > http://www.sqlite.org/atomiccommit.html) and concurreny issues only > affect writers (readers are fully concurrent; > http://www.sqlite.org/lockingv3.html, > http://www.sqlite.org/faq.html#q6), so my question really was more > directed to real-world experiences with rt3 and SQLite rather than > rumours :)
It wasn't the last time I looked at it. I still wonder about transaction isolation levels, but as long as RT doesn't use BEGIN, COMMIT or ROLLBACK, I guess that doesn't matter much. -- -- Tom Lahti, SCMDBA, LPIC-1 BIT LLC (425)251-0833 x 117 http://www.bitstatement.net/ -- _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
