Re: Automatic Integrity Checks

sjg_at_qdot.qld.gov.au writes in article <31n6s9$10p_at_camelot.qdot.qld.gov.au>:
>
> I am posting this on behalf of a colleague investigating
> methods to automate integrity checks using Dictionary constraints
> as the starting point. (Oracle 6.0.37)
>
> We are developing under V6 with a view to eventual V7 migration.
> The plan is to produce a working system under V6 and take
> advantage of V7 features like enabled constraints later.
> Under V6 we need to generate code to detect and highlight
> records which violate constraints, and store the error rec
> id's in an exception table (a la V7). The script generated
> would be run against numerous production instances as required.
>
>

I would strongly suggest going to V7 immediately, because integrity checking might be implemented in V7 in other ways than you expect.

For example, CASE Generator can generate constraint checking at commit time. With DB constraints, checking is the time the database gets the DML statements... this can lead to difficulties in your application.

Willy

Willys Mail     FidoNet   2:2474/117  2:2474/118     Mail Only System
                CIS: 100020,3517       USR Courier HST dual standard
                willyk_at_kbigate.franken.de
                willyk_at_kbigate.stgt.sub.org
                ->   No Request from 06.00 to 08.00 <-
======================================================================