<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>No error processing on DB operations</title>
		<link>http://wikipbx.subwiki.com/forum/t-248297/no-error-processing-on-db-operations</link>
		<description>Posts in the discussion thread &quot;No error processing on DB operations&quot; - Error processing on DB operations</description>
				<copyright></copyright>
		<lastBuildDate>Mon, 06 Feb 2012 00:42:29 +0000</lastBuildDate>
		
					<item>
				<guid>http://wikipbx.subwiki.com/forum/t-248297#post-810041</guid>
				<title>Re: No error processing on DB operations</title>
				<link>http://wikipbx.subwiki.com/forum/t-248297/no-error-processing-on-db-operations#post-810041</link>
				<description></description>
				<pubDate>Wed, 16 Jun 2010 18:15:28 +0000</pubDate>
				<wikidot:authorName>stas_shtin</wikidot:authorName>				<wikidot:authorUserId>230176</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Django 1.2 supports <a href="http://docs.djangoproject.com/en/dev/ref/models/instances/#validating-objects">model validation</a> that handles duplicate field errors among other things. Wikipbx version that supports recent django is not production ready yet. So the only way to make sure there's no DB error for current version is to work on this yourself.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://wikipbx.subwiki.com/forum/t-248297#post-809901</guid>
				<title>No error processing on DB operations</title>
				<link>http://wikipbx.subwiki.com/forum/t-248297/no-error-processing-on-db-operations#post-809901</link>
				<description></description>
				<pubDate>Wed, 16 Jun 2010 14:35:10 +0000</pubDate>
				<wikidot:authorName>ledda</wikidot:authorName>				<wikidot:authorUserId>497236</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I'm checking wikipbxweb/views.py and there is no error checking on any DB operations.<br /> It's always assumed that creation, deletion, saving… passed fine.<br /> Unfortunately, in real life it is not, and customer is getting Django debug output or apache internal error page.</p> <p>Is there any plans to adjust this?</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>
