Hi,
Sean Davis schrieb:
> No problem. I was thinking that you had a bunch of data that you
> wanted to load ONCE, clean up, and then you would NOT be inserting
> duplicated values. If you are going to be inserting duplicates
> potentially with every insert, I think that a trigger is the only way
> to go on the DB side of things. Of course, you could do things on the
> client side, as well (do a lookup, find nothing--do insert, find
> something--do nothing or do update).
Thanks for your opinion. Then I'll go with a trigger.
Regards,
Verena
