Order of Transactions

I am trying to find a good way to determine the order in which rows in specific tables are inserted, updated, and deleted. I started with and Oracle sequence but found that the order of the sequence number assigned to my log table by triggers does not always match the order that the rows got committed. I was thinking of replacing the Oracle sequence with my own version that reads a number from a table adds one and updates the number for next time. Since all users share the same table and the trigger code that reads and updates the number is in the same transaction this should yield truly sequential number assignment for the log. Seems like some performance problems could result from doing this.

Has anyone had a similar problem? How did you solve it?

Thanks,

Matthew MacFarland
Dril-Quip, Inc.
matthew_macfarland_at_dril-quip.com Received on Wed Oct 07 1998 - 22:49:24 CEST