On Wed, Oct 6, 2010 at 7:56 PM, Graham Higgins <[email protected]> wrote: > SQLite is not the best choice in a multi-threaded context. The issues is > discussed in the Storm manual: > > https://storm.canonical.com/Manual#Managing%20stores > > Most of which I cribbed for an article on Storm and Pylons: > > http://bel-epa.com/notes/Pylons/StormandPylons.xml > > Alternatively, you could try the Pylons-specific Zope tm-mediated approach > that Canonical suggest: > > https://storm.canonical.com/PylonsRepoze.tm2
Thanks for the links. I'm already aware that SQLite sucks at muti-threaded, but I haven't had problems with it before. This is supposed to be a simple CRM app, so I didn't want to have clients deploy large systems like Postgres (to which I had to switch). I've also hunted down some bugs in my own code (was actually using two stores by mistake in the same thread). So it should now work correctly with Postgres after I patch that up. > Or Vsevolod Balashov's "middlestorm" WSGI app > > http://pypi.python.org/pypi/middlestorm/0.8.1 Hey! You found my missing footnote! :D -- Branko Vukelić [email protected] [email protected] Check out my blog: http://www.brankovukelic.com/ Check out my portfolio: http://www.flickr.com/photos/foxbunny/ Registered Linux user #438078 (http://counter.li.org/) I hang out on identi.ca: http://identi.ca/foxbunny Gimp Brushmakers Guild http://bit.ly/gbg-group -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
