<?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: Triggers&#8230;</title>
	<atom:link href="http://technology.amis.nl/blog/3162/triggers/feed" rel="self" type="application/rss+xml" />
	<link>http://technology.amis.nl/blog/3162/triggers</link>
	<description>Weblog for the AMIS Technology corner</description>
	<lastBuildDate>Fri, 10 Feb 2012 16:47:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bert Jan Meinders</title>
		<link>http://technology.amis.nl/blog/3162/triggers/comment-page-1#comment-319889</link>
		<dc:creator>Bert Jan Meinders</dc:creator>
		<pubDate>Fri, 16 May 2008 08:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=3162#comment-319889</guid>
		<description>Perhaps I misunderstand the problem but why not simply disable all required triggers, run the update code and enable them again, regardless the outcome of the update script???</description>
		<content:encoded><![CDATA[<p>Perhaps I misunderstand the problem but why not simply disable all required triggers, run the update code and enable them again, regardless the outcome of the update script???</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Wolf</title>
		<link>http://technology.amis.nl/blog/3162/triggers/comment-page-1#comment-318436</link>
		<dc:creator>Patrick Wolf</dc:creator>
		<pubDate>Mon, 12 May 2008 11:04:15 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=3162#comment-318436</guid>
		<description>Hi Patrick, you could also add the check for NOT(bar_semaphore.sem_emp) into the WHERE clause of the trigger. That might make it even faster. But to be honest, I haven&#039;t tested that.

Patrick</description>
		<content:encoded><![CDATA[<p>Hi Patrick, you could also add the check for NOT(bar_semaphore.sem_emp) into the WHERE clause of the trigger. That might make it even faster. But to be honest, I haven&#8217;t tested that.</p>
<p>Patrick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DJ</title>
		<link>http://technology.amis.nl/blog/3162/triggers/comment-page-1#comment-318297</link>
		<dc:creator>DJ</dc:creator>
		<pubDate>Sun, 11 May 2008 21:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=3162#comment-318297</guid>
		<description>On a second thought, your &quot;solution&quot; did not actually disable the trigger at all. Even if a trigger body with only &quot;null;&quot; in it will incur much more overhead than without the trigger at all. If your customer wants the triggers to be re-enabled, regardless of the status of overnight job, then the update script should re-enable the triggers and send an error that the job failed.</description>
		<content:encoded><![CDATA[<p>On a second thought, your &#8220;solution&#8221; did not actually disable the trigger at all. Even if a trigger body with only &#8220;null;&#8221; in it will incur much more overhead than without the trigger at all. If your customer wants the triggers to be re-enabled, regardless of the status of overnight job, then the update script should re-enable the triggers and send an error that the job failed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DJ</title>
		<link>http://technology.amis.nl/blog/3162/triggers/comment-page-1#comment-318295</link>
		<dc:creator>DJ</dc:creator>
		<pubDate>Sun, 11 May 2008 21:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=3162#comment-318295</guid>
		<description>MINVALUE???
Ever heard of a function called LEAST?</description>
		<content:encoded><![CDATA[<p>MINVALUE???<br />
Ever heard of a function called LEAST?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

