|           A Data Quality Assurance Example
|
|  Development programmers share a ''production'' database
|
|  The production database must only contain clean data
|
|  But the development programmers need to insert and delete test data
|
|  So, we provide the developers with their own view of the main data tables,
|  supported by auxiliary tables showing what they have ''added'' and ''deleted''
|
|  The following SQL can support the developer view of a table:
|
|  select C.NAME,C.DEPT from CLEAN_EMP C
|    where not exists
|      ( select D.NAME,D.DEPT from DEV_EMP_DELETED D
|                  where D.NAME=C.NAME and D.DEPT=C.DEPT )
|                       union select NAME,DEPT from DEV_EMP_ADDED;
|


|        You can run these rules in a browser, using the Internet Business Logic system
|                          at  www.reengineeringllc.com



developer added a row some-empname some-dept to his view of the clean table
----------------------------------------------------------------------------
developer view of the clean table has a row that-empname that-dept


clean table has a row some-empname some-dept
not : developer deleted a row that-empname that-dept from his view of the clean table
-------------------------------------------------------------------------------------
developer view of the clean table has a row that-empname that-dept


clean table has a row this-empname this-dept
=================================================
                       Fred Clean   Credit Rating
                       Jean Clean   Receivables


developer added a row this-empname this-dept to his view of the clean table
===========================================================================
                       Joe Hacker   IT


developer deleted a row this-empname this-dept from his view of the clean table
===============================================================================
                        Fred Clean   Credit Rating