This content has been marked as final. Show 1 reply
There is no support for modifying historical data as it is read-only. Although nothing prevents _LT updates, it is not supported as all dml should be through the created view. As a result, you can not set a column as 'not null' within beginDDL/commitDDL due to these historical records. Would it be possible to leave the column as nullable and enforce it for any future dml within a trigger. You could also update any existing data. Then for any historical records, you could create a function to compute the value as needed (if this is even possible?).
SQL> select nvl(column_name, function_to_compute_column(<necessary parameters>)) from ...
Obviously, this might not work if it depends on more than just the other row values. If you give me more details on how the column is computed, I might have further suggestions.