Caché Upgrade Checklists - InterSystems Documentation

Caché 2008.2 Upgrade Checklist7.2.7.16 Compilation Checks Field Names In MapsIn prior versions, the class compiler did not complain about references to nonexistent properties in the CacheSQLStoragemap. Now, a non-existent field that is part of an expression in a map subscript will be reported as an error during classcompilation.The compiler now also checks that all field references are of the form schema.fieldname and that the schema is correct.7.2.7.17 Privilege Checking Extended To Functions Called From QueriesBeginning in this version, Caché SQL now checks to see if the user executing a query has the privilege to execute anyprocedures called as user-defined SQL functions in that query. The user must have EXECUTE privilege on the functionsprocedure in order to execute the SQL statement that calls it. For example, to execute the query:SELECT A, B, MyFunction() from SQLUser.MyTablethe user will need SELECT privilege on the SQLUser.MyTable table and EXECUTE privilege on the SQLUser.MyFunctionprocedure.Note:As with all other SQL privilege checking, this only applies to SQL prepared and executed via ODBC, JDBC, orany flavor of Dynamic SQL. It does not pertain to Objectscript embedded SQL, “&sql( ... )”.7.2.7.18 Long Fields In xDBC QueriesIf a class defines a property of type %Library.String, and the MAXLEN for this property is greater than 16374, when thisfield is selected in a query over ODBC or JDBC, only the first 16374 characters of the field will be returned. To supportdata in a single field longer than 16374 characters, use a stream datatype in place of the string.CAUTION:Current ODBC and JDBC drivers have differing limits on the maximum length of returned columns. Forthose used with Caché, customers should assume that the maximum length returned by a query is 4096characters.7.2.7.19 Change To Conversion Of SQLBINARY, SQLVARBINARY And SQLLONGVARBINARYThe behavior for conversions of SQLBINARY, SQLVARBINARY, and SQLLONGVARBINARY has changed. It nowreturns two character hex values for each byte of data returned as SQL_C_CHAR and SQL_C_WCHAR.The algorithm used in prior releases could result in erroneous conversions and/or incorrect string lengths. This causedproblems for WinSQL when displaying SQLLONGVARBINARY columns. This change alters the behavior when usingSQLFetch and SQLGetData for columns using these datatypes. The behavior now matches what is seen with SQLServerdata.7.2.8 CSP Changes7.2.8.1 Properties Of %request Marked Read-OnlyModifying some properties of the %request object that are provided by the CSP gateway would cause the next request inthe same process to also show this modified value. This could result in subtle errors in the application. To ensure thisproblem does not occur, this version of Caché now marks the following %CSP.Request properties as read only: UserAgent,ContentType, CharSet, Method, Protocol, Secure, GatewayApplication, GatewayConnectionName, GatewayBuild,GatewaySessionCookie, GatewayInstanceName, and CSPGatewayRequest.192 Caché Upgrade Checklists