<?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: Using Oracle 11g Virtual Columns for implementation of Dynamic Business Rules</title>
	<atom:link href="http://technology.amis.nl/2007/10/05/using-oracle-11g-virtual-columns-for-implementation-of-dynamic-business-rules/feed/" rel="self" type="application/rss+xml" />
	<link>http://technology.amis.nl/2007/10/05/using-oracle-11g-virtual-columns-for-implementation-of-dynamic-business-rules/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=using-oracle-11g-virtual-columns-for-implementation-of-dynamic-business-rules</link>
	<description></description>
	<lastBuildDate>Fri, 12 Apr 2013 10:04:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Eric van Mourik</title>
		<link>http://technology.amis.nl/2007/10/05/using-oracle-11g-virtual-columns-for-implementation-of-dynamic-business-rules/#comment-4936</link>
		<dc:creator>Eric van Mourik</dc:creator>
		<pubDate>Fri, 05 Oct 2007 09:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=2427#comment-4936</guid>
		<description><![CDATA[Lucas, interesting post. After reading your previous post about virtual columns I had some similar thoughts about using virtual columns for business rule validation.

What about just adding a generic RECORD_IS_VALID virtual column to a table? With - as you suggest - a check constraint to ensure that the value of the virtual column is always &quot;Y&quot;.
If we base the value of that virtual column on a &quot;validate_record&quot; function that accepts the values of all &quot;real&quot; columns of the table, this &quot;validate_record&quot; function could be a generic &quot;hook&quot; to other functions that do the actual checking of individual rules. A kind of alternative framework for business rule checking, that does not clutter up table definitins too much. Just some thoughts...

Regards,
Eric]]></description>
		<content:encoded><![CDATA[<p>Lucas, interesting post. After reading your previous post about virtual columns I had some similar thoughts about using virtual columns for business rule validation.</p>
<p>What about just adding a generic RECORD_IS_VALID virtual column to a table? With &#8211; as you suggest &#8211; a check constraint to ensure that the value of the virtual column is always &#8220;Y&#8221;.<br />
If we base the value of that virtual column on a &#8220;validate_record&#8221; function that accepts the values of all &#8220;real&#8221; columns of the table, this &#8220;validate_record&#8221; function could be a generic &#8220;hook&#8221; to other functions that do the actual checking of individual rules. A kind of alternative framework for business rule checking, that does not clutter up table definitins too much. Just some thoughts&#8230;</p>
<p>Regards,<br />
Eric</p>
]]></content:encoded>
	</item>
</channel>
</rss>
