Re: database integrity

From: mountain man <hobbit_at_southern_seaweed.com.op>
Date: Thu, 26 May 2005 07:14:52 GMT
Message-ID: <MHele.1567$BR4.243@news-server.bigpond.net.au>

"Kenneth Downs" <knode.wants.this_at_see.sigblock> wrote in message news:1v8em2-og2.ln1_at_pluto.downsfam.net...
> mountain man wrote:

>> "Kenneth Downs" <knode.wants.this_at_see.sigblock> wrote in message

>>> Hmmmm. In a prior life ...

...[trim]...

>>> Now the real trick question is, how do you build constraints that apply
>>> only
>>> to new data?
>>
>>
>> The contraints would be conditional, and the conditional expression
>> would seek reference to (for example) a date of entry to the system
>> or some other parameter which could service the requirement to
>> differentiate what you want to call "new" from that which is "existent"
>> or "not-new".
>>
>
> Why not just fire some constraints on INSERT, others on UPDATE and so
> forth.
> Or is this what you mean by conditional?

Yes, put in a concise manner.

Pete Brown
Falls Creek
Oz
www.mountainman.com.au Received on Thu May 26 2005 - 02:14:52 CDT