Will importing rows into a table fire the triggers on the target table?
Printable View
Will importing rows into a table fire the triggers on the target table?
If it is enabled, yes.Quote:
Originally posted by JMac
Will importing rows into a table fire the triggers on the target table?
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
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...
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.
mariest there is no direct in imp!
yep. only direct export.Quote:
Originally posted by pando
mariest there is no direct in imp!
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...
Well direct only works in export, import will always do insert anyway not writing directly to data block
hmm, maybe was sql*loader direct=y. maybe I was just dreaming...
hm I wish we can do import direct=true as well heh so I can get more sleeps :D
Dropped the user (and their objects)
Re-created the tables, sequences, functions etc.
Did NOT re-create the constraints or triggers.
Did the import - fine!
Re-created the contstraints and triggers - and Hey presto! It works fine.
But there must be an easier way? If people use exports as a sort of back-up do they have disable constraints and db triggers to get the data back into the db?
Thanks anyway Guys
JMac