Subject | Re: [Firebird-Architect] rfc: TRUNCATE TABLE |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2008-10-19T14:40:22Z |
Vlad Khorsun wrote:
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.
If you talk about different transactions for truncate related
(referential constraints) tables, you're thinking on different approach.
So what is it?
Adriano
>> It seems as an important feature for me. Otherwise you will can'tI think I don't understood you, or you didn't understood I.
>> 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 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.
If you talk about different transactions for truncate related
(referential constraints) tables, you're thinking on different approach.
So what is it?
Adriano