Tack Changes on DML SQL Files
Part of our deployment includes the population of certain key metadata elements that are inserted in the relevant tables by running DML SQL scripts as INSERT statements during installation.
We wanted to validate of Source Control for Oracle would not only track down changes done at the DDL level, to the corresponding SQL DDL file on Azure DevOps, but if it will also track any changes into the metadata inserted into the underlying tables via DML and would ALSO track and make the necessary changes to the SQL DML files.
My gut feeling is that the tool would only detect changes done at any Oracle object type, but purely at a DDL level and not be able to detect changes to the underlying loaded data and correctly identify which DML SQL files need to have their INSERT statements updated to match the newly inserted data directly on top of the DB.
In short, the intelligence of the tool works only for DDL, but not for any DML.
0 · Share on Twitter