Re: long transaction

>
> have you considered im****ting to a tem****ary 'holding' table with
> copy, then doing 'big' sql statements on it to check constraints, etc?
>

Yes I considered it, but the problem is the data is very tight related 
between different tables and is im****tant to keep the im****t order of each

entity into the database. With other words, the entity imprt serialization

is mandatory. In fact the im****t script doesn't keep just insert but also 
delete and update for different entities. So copy is not enough. Also
using 
'big' sql statements cannot guarantee the im****t order.

Sabin