[Dagnabitt]

If the triggering statement of a BEFORE statement trigger is an UPDATE or DELETE statement that conflicts with an UPDATE statement that is running, then the database does a transparent ROLLBACK to SAVEPOINT and restarts the triggering statement. The database can do this many times before the triggering statement completes successfully. Each time the database restarts the triggering statement, the trigger fires. The ROLLBACK to SAVEPOINT does not undo changes to package variables that the trigger references. To detect this situation, include a counter variable in the package.

[2ndDivisionVet]

Ouch!

[lee martell]

What? If that is a real sentence of instruction, then I feel as dazed and confused as Madam Shrek here. That sentence was never meant to be diagrammed, IMO.

[fella]

But . . . . But . . . . We was told dat dat Bell Curve books was nots tru an is raceist besides. An it aint kools to be acting likes whitey and learnings stuff in school.

[Still Thinking]

Are you speaking in cursive?

[shibumi]

Anyone for a game of "Hungry Hippos?"

[SandwicheGuy]

If the triggering statement of a BEFORE ... include a counter variable in the package.

I don't know how many people here can understand data base terminology (DBase II here)) but they don't have to be coders to understand juxtaposition... That was brilliant!! I am still smiling. Am I bad?

[lefty-lie-spy]

Yup, its real. Lots of technical documentation is written just like that for the techies that consume it. There’s no way to write it much simpler in many cases.

[raybbr]

To detect this situation, include a counter variable in the package.

Why didn't you just do that in the first place? Sheesh! :)

[Old Yeller]

Better work on understanding cursive writing before you try tackling nested ifs.

[Maceman]

If the triggering statement of a BEFORE statement trigger is an UPDATE or DELETE statement that conflicts with an UPDATE statement that is running, then the database does a transparent ROLLBACK to SAVEPOINT and restarts the triggering statement. The database can do this many times before the triggering statement completes successfully. Each time the database restarts the triggering statement, the trigger fires. The ROLLBACK to SAVEPOINT does not undo changes to package variables that the trigger references. To detect this situation, include a counter variable in the package.

Well duh.