yes, I suspect its a bad idea!
I'm working with an application that was modeled incorrectly. a status history table had been modeled with a primary key on a business key and the effective date instead of the end date of the status record. there is only one status possible at a time.
logic was developed to insert new status records with null end dates and then a trigger was provided that populated all end dates except the one with the MAX(ROWID). so, the expectation is that ROWID will always get bigger.
now the database has been moved in promotion environments using data pump. in our development environments it still seems to be working. but not in the clients promotional environments.
my question is: is there a setting associated with data pump that the client has used that is not respecting ROWID the way it has in our development environment?
I'm trying to identify whether there is a way to continue to use the old code without immediate re-development.
thanks in advance for your input.