8. Installing and Testing Data Types : Testing the New Data Type Code
 
Share this page                  
Testing the New Data Type Code
Because your code runs as part of the DBMS Server, any bugs in your code can have severe consequences to the system. To avoid damaging production data, run your code in a test installation before you install it in the production installation.
Symbols within the DBMS Server are not available for customer use.
Because it is inconvenient during testing to have to shut down and restart an entire installation to check out the system, Ingres has provided the field add_risk_consistency in the IIADD_DEFINITION structure. If set to the value IIADD_INCONSISTENT, this flag allows the system to startup when a newly started process does not agree with the remainder of the Ingres installation.
Caution!  Running with the add_risk_consistency set to IIADD_INCONSISTENT risks the data integrity of all databases in that installation. If failures occur, it is possible that the DBMS Server cannot back out transactions from any database. This flag must be used with extreme care and must never be used in a production environment.