> I would like to see something from Jan too...
> My opinion is that RI _MUST_ be implemented in 6.6.
> There are 3 ways:
>
> 1. Using deferrable rules/statement level triggers.
> 2. Using transaction log (to read changes made in
> parent/child tables and check RI constraints).
> 3. Using DIRTY READ in refint.c
>
> I hope to be able to do 2. or 3., though it would be much
> better to have 1. (with statement level triggers) implemented by Jan.
Uh, oh. Vadim has thrown down the hachet on a 6.6 _must_ _have_ item.
(I agree with him, but am glad I didn't have to do it.)
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026