13.07.2015 Views

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Caché</strong> 2010.2 <strong>Upgrade</strong> ChecklistThe ^%SYS("SourceControlClass", ) was always in the search path when looking up the source control class,so this will work on older versions of <strong>Caché</strong>. The change is that the method that updates the class will now set this nodeand clear the ^SYS("SourceControlClass") node.Also when looking up the source control path, the locations examined have been changed to this order:1. ^%SYS("SourceControlClass", )2. ^SYS("SourceControlClass")3. ^%SYS("SourceControlClass")4.2.2 Routine Compiler Changes4.2.2.1 Macro Preprocessor Return Values ChangedIn this version, a change has been made in the macro preprocessor behavior when compiling code that contains SQLstatements. Prior to this change if a SQL statement failed to compile, the preprocessor would report the error and stop; nocode was produced.The new behavior is to report the error but continue to compile the code and return the result to the caller of the preprocessor.When a SQL statement fails to compile, the generated code produced isX "** SQL Statement Failed to Compile **"If the method or routine containing the erroneous SQL statement is ever run, the attempt to execute the SQL statement willresult in an error message at runtime. This change means when compiling classes with methods that contain embeddedSQL statements that fail to compile, the errors will be reported, but the methods will still be generated.Note:This behavior will not occur for a “&sql(DECLARE CURSOR ...)” statement because DECLARE CURSORproduces no code itself. Furthermore, this new behavior is not in effect when the <strong>Caché</strong> system compiles cachedquery routines.4.2.3 Class Changes4.2.3.1 BuildValueArray Now Marked As FinalSubvalue indexes can be defined using property elements and keys. If the property is a collection, the element values correspondto the elements of the collection and key values correspond to the position (for lists) or key (for arrays). For propertiesthat are not collections, elements and keys correspond to subscripts and values as contained in a "value array". Thevalue array is constructed by a property method, BuildValueArray.If applications had overridden BuildValueArray, the results were ignored when the object was stored, and the index(es)were not updated. This is incorrect.Beginning with this release BuildValueArray is generated automatically for collection properties and marked as Final;therefore, it cannot be overridden by subclasses.4.2.3.2 %Text Parsing Of Hyphens And Negative Numbers ImprovedThis version of Cache' improves the parsing of hyphen/minus sign so that “–” is parsed as a negative number, andso that “––” is parsed as a positive number (digits). In addition, complex non-numeric sequences such as “Section3-4.2-2” are now parsed as “Section 3 4.2 2”; the sequence 3-4.2-2 is not treated as a numeric just because it contains allnumeric characters.78 <strong>Caché</strong> <strong>Upgrade</strong> <strong>Checklists</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!