vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I'm looking into triggers as a potential fix to a problem I'm having at work. The basic situation is that we are using db2 replication, and if something goes wrong, there is the chance that a unique key that lies outside of the primary key. Anyhow to make a long story short, every time this happens replication breaks and is then down and the problem compounds until it is fixed. I'm currently looking at several solutions, one that I think might work is triggers. I would write a before insert trigger that looks at the database and sees if it is going to violate the unique key constraint and if it is, write out a log, send an email and then drop it on the floor. This is the part that I'm not sure I can do. Is there a way for a DB2 to not process an insert while not throwing an error as to break replication? Any help will be greatly appreciated. -Charles |