Will an IMPORT fire database triggers?

[JMac]

Will importing rows into a table fire the triggers on the target table?

[julian]

Originally posted by JMac
Will importing rows into a table fire the triggers on the target table?

If it is enabled, yes.

[aarroyob]

Hi,

It depends, I explain:

If your table and trigger are created, yes the import fire up your triggers.

If you drop the table and is the import file who create the table, no because the trigger always are created after the row's import.

Best regards

Angel

[marist89]

In the back of my mind, I am thinking that DIRECT=y imports don't fire triggers, but I can't back it up with a link...

[JMac]

Think I need to disable all triggers and constraints - do the IMPORT (I know the data is pukka as it was created in a DB with these constraints and triggers) - then enable all the triggers and constraints.

If anyone can tell me the best IMPORT/EXPORT syntax to use in future I'd be grateful.

[pando]

mariest there is no direct in imp!

[vinit]

Originally posted by pando
mariest there is no direct in imp!

yep. only direct export.

[marist89]

OK, I really meant to say: When importing a export file that was exported with DIRECT=Y, I don't think that triggers are fired...

[pando]

Well direct only works in export, import will always do insert anyway not writing directly to data block

[marist89]

hmm, maybe was sql*loader direct=y. maybe I was just dreaming...