Subject | Re: [Firebird-Architect] rfc: TRUNCATE TABLE |
---|---|
Author | Vlad Khorsun |
Post date | 2008-10-19T16:02:59Z |
>>> It seems as an important feature for me. Otherwise you will can'tYes, it was not clear from your previous post. Your idea seems good.
>>> truncate a set of related tables if you don't drop the referential
>>> constraints first.
>>>
>>
>> We can but not in the same transaction and statements must be ordered.
> I think I don't understood you, or you didn't understood I.
>
> I mean that if you put verification of referential constraints in DFW,
> there you can verify if all related tables are being truncated, so the
> statements don't need to be ordered.
But what we can do, if master table truncated OK, but child failed ?
I'm not sure it can happen (except of hardware failures) as we can perform
all checks in phase 1 and real truncation in phase 3...
Regards,
Vlad