<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SQLite3: Beware of Concurrency</title>
	<atom:link href="http://alexlod.com/2008/10/14/sqlite3-beware-of-concurrency/feed/" rel="self" type="application/rss+xml" />
	<link>http://alexlod.com/2008/10/14/sqlite3-beware-of-concurrency/</link>
	<description>A blog by Alex Loddengaard</description>
	<lastBuildDate>Mon, 06 Feb 2012 21:25:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alex Loddengaard</title>
		<link>http://alexlod.com/2008/10/14/sqlite3-beware-of-concurrency/comment-page-1/#comment-3261</link>
		<dc:creator>Alex Loddengaard</dc:creator>
		<pubDate>Sat, 20 Dec 2008 05:37:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexloddengaard.com/?p=750#comment-3261</guid>
		<description>SQLite3 is great for read-only stuff.  It&#039;s ultra fast for single-table SELECTs.</description>
		<content:encoded><![CDATA[<p>SQLite3 is great for read-only stuff.  It&#8217;s ultra fast for single-table SELECTs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan W</title>
		<link>http://alexlod.com/2008/10/14/sqlite3-beware-of-concurrency/comment-page-1/#comment-3259</link>
		<dc:creator>Jordan W</dc:creator>
		<pubDate>Sat, 20 Dec 2008 04:20:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexloddengaard.com/?p=750#comment-3259</guid>
		<description>AAAHHHH.. This is so old but thanks for the heads up! Will stay clear of sqlite.</description>
		<content:encoded><![CDATA[<p>AAAHHHH.. This is so old but thanks for the heads up! Will stay clear of sqlite.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Loddengaard</title>
		<link>http://alexlod.com/2008/10/14/sqlite3-beware-of-concurrency/comment-page-1/#comment-2393</link>
		<dc:creator>Alex Loddengaard</dc:creator>
		<pubDate>Thu, 06 Nov 2008 14:59:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexloddengaard.com/?p=750#comment-2393</guid>
		<description>Increasing the lock timeout seems like a terrible solution that should absolutely not be used in production.  You&#039;re asking for deadlock.</description>
		<content:encoded><![CDATA[<p>Increasing the lock timeout seems like a terrible solution that should absolutely not be used in production.  You&#8217;re asking for deadlock.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: foo</title>
		<link>http://alexlod.com/2008/10/14/sqlite3-beware-of-concurrency/comment-page-1/#comment-2387</link>
		<dc:creator>foo</dc:creator>
		<pubDate>Thu, 06 Nov 2008 08:30:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexloddengaard.com/?p=750#comment-2387</guid>
		<description>Just increase the lock timeout. See the patch at http://code.djangoproject.com/ticket/9409 for docs.</description>
		<content:encoded><![CDATA[<p>Just increase the lock timeout. See the patch at <a href="http://code.djangoproject.com/ticket/9409" rel="nofollow">http://code.djangoproject.com/ticket/9409</a> for docs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Aller</title>
		<link>http://alexlod.com/2008/10/14/sqlite3-beware-of-concurrency/comment-page-1/#comment-1971</link>
		<dc:creator>Max Aller</dc:creator>
		<pubDate>Thu, 16 Oct 2008 16:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexloddengaard.com/?p=750#comment-1971</guid>
		<description>That&#039;s why unless you&#039;re doing anything but read-heavy operations all the time, you use InnoDB with MySQL ;)</description>
		<content:encoded><![CDATA[<p>That&#8217;s why unless you&#8217;re doing anything but read-heavy operations all the time, you use InnoDB with MySQL ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

