Ingres 9.2 Migration Guide - Actian

Considerations for Ingres 6.4Journaling On by DefaultGreater Sensitivity to Arithmetic Errors4GL TABLE_KEY Type ConversionsIn Ingres 6.4, if a database was journaled, a newly-created table would not bejournaled unless WITH JOURNALING was explicitly stated.In Ingres, journaling is on by default. This means that if an application createstemporary tables, those tables will be journaled; this may consume moresystem resource, resulting in Ingres applications running more slowly thanexpected.You can turn default journaling off by changing the Configuration-By-Formsparameter “default_journaling.” Alternative options are to issue a SETNOJOURNALING statement at the beginning of an application, createtemporary tables WITH NOJOURNALING, or use session tables.Ingres 6.4 ignores a number of arithmetic error conditions (such as floatingpoint overflow and divide-by-zero). Ingres correctly reports arithmetic errorson all platforms. If an application generates arithmetic exceptions when testedwith Ingres, it is probable that the application had problems in Ingres 6.4 thatwere not reported. The application must be corrected.Conversion of 4GL VARCHAR variables to the TABLE_KEY type gives lengtherrors. Avoid this by converting to char first:TABLE_KEY(CHAR(varcharVariable))User-Defined Data Type ChangesSome 6.4 releases of 4GL had problems with variables of type TABLE_KEY. Ifyou were doing type conversions to avoid the use of TABLE_KEY variables,consider removing the conversion altogether and using the TABLE_KEY typedirectly.If you are using Object Management Extension to declare user-defined datatypes in the server, be aware of some changes in calling sequences. Fordetails, see the Object Management Extension User Guide.92 Migration Guide