Caché Upgrade Checklists - InterSystems Documentation

Caché 2010.1 Upgrade Checklist5.2.6.16 Names Limited To 180 CharactersCompiled classes are stored in globals indexed by the package name, class name and component name. When each of theseis a long string of characters, there is the possibility that the maximum length for a global subscript will be exceeded. Toreduce the likelihood of this happening, this version of the compiler imposes a maximum size limit on the names of methods,parameters, and properties declared in a class. That limit is 180 characters.5.2.6.17 Stored Procedure Return Parameter Types CheckedPrior to this version, return value type parameters were ignored. Beginning with this version, the return type parameters ofa class method are now honored by the stored procedure projection. For example,classmethod myproc() as %String(MAXLEN=100) [ sqlproc ] {...}will now project the xDBC column with a maximum string length of 100. Previously, it would have used the default of 50,5.2.7 Object Binding Changes5.2.7.1 Change In Properties Projected For JalapeñoPrior to this version, all properties that are defined in Caché class that are not marked as Private or ServerOnly, or otherwisenot projectible, are present in Java POJO class. Now, properties with names starting with “%” will not be projected inPOJO. This will affect user classes if they have properties whose name begin with “%”.5.2.8 SQL Changes5.2.8.1 Changed Handling Of Procedures Names In Embedded SQLIn this version, Caché now treats unqualified procedures names in the &SQL statement differently from prior versions. Theschema name used for unqualified procedure names now takes into account any #import value defined. This means if youhave an embedded SQL CALL statement (“&SQL( ... )”) in a class method and the procedure name is unqualified, thedefault will be the schema that maps to the package of the current class. Previously, the default schema would be the systemdefineddefault schema. The default schema for DDL statements remains the system defined-default schema.5.2.8.2 Support For SQL Extension FOR ALL RemovedIn this version, support for the FOR ALL statement has been removed. In version 2009.1, it was deprecated. Any applicationusing FOR ALL will need to be modified. If necessary, the FOR ALL statement may be converted into aNOT FOR SOME ...statement with a condition carefully constructed to achieve the desired result.5.2.8.3 Date And Time Conversion Errors Now Reported In SQL StatementsIn an SQL statement that takes a %Date value as input in either DISPLAY mode or ODBC/JDBC mode, if the input valuecannot be converted to a valid Logical %Date value, the SQL statement will return SQLCODE=-146. For similar errorsinvolving %Time values that cannot be converted, SQLCODE=-147 will be returned. For example,&sql(select name into :name from sample.person where dob = '02/29/2009')will return “SQLCODE=-146 Unable to convert Date input to a valid Logical Date value”.124 Caché Upgrade Checklists