Caché Upgrade Checklists - InterSystems Documentation

Caché 2008.2 Upgrade Checklist7.2.10 Caché Terminal Changes7.2.10.1 Cache Terminal Local Network Encoding ChangedThe Caché Terminal local connection default network encoding has been changed to UTF8 in 8-bit installs to be consistentwith the default Caché server default value.7.2.10.2 Changes To Terminal Connection Display When Invoked From ScriptsBeginning with version 5.1, a Caché terminal session would begin by displaying the Node and Instance name that was theendpoint of the connection. It was done so a customer connecting to a machine via telnet would get a confirmation indicationthat they connected to the correct instance. However, this caused some existing customer scripts to fail because the displayof the node and instance could throw off the parsing of the output.In this version, the terminal will not display the node and instance if a routine is passed in on the command line, forexample,csession cache -U%SYS ALL^%FREECNTsince the process entering Caché is already on the correct node, and specifies the correct instance on the command line. Inall other circumstances, the node and instance names will be displayed.7.2.11 Standardize UNIX® Names For ODBCInterSystems is standardizing on iODBC for building our narrow and wide ODBC dependent projects. Cgate is alreadyusing an "i" or "u" suffix to designate iODBC and unixODBC respectively. A "w" suffix will designate a wide or Unicodeversion of the library.The file, libcacheodbc, will continue to be the narrow version of the InterSystems ODBC driver using iODBC headers, butlibcacheodbciw will be the Unicode version of the InterSystems ODBC driver supporting iODBC.Currently the narrow version of cgate and libcacheodbc will remain the default working executables in shipped examples.It is up the user to configure to use the Unicode versions of cgateiw or libcacheodbciw if needed.Note:Mac platforms require a special link operation on libcacheodbciw to support the cppbinding and that will be calledlibcacheodbcmiw.7.2.12 Language Binding Changes7.2.12.1 Light C++ Binding Reference Count Behavior ChangedPrior to this change, if openid() was called twice for the same class and id, and the results assigned to two different lc_d_ref's,those lc_d_ref's pointed to two separate projection objects in memory, each initialized with property values from the samedatabase object. Setting new property values using one would not affect the other. If changes made to one were saved, andthen changes made to the other were saved, the property values from the last-saved projection object would overwrite thosefrom the previously-saved projection object.Similarly, if a projection object returned by create_new() was assigned to an lc_d_ref and saved to the database, and openid()was then called for that class with the id of the newly-saved object, and the result assigned to a second lc_d_ref, the twolc_d_ref's would point to two separate projection objects in memory.This version changes the semantics of the Light C++ Binding object references (lc_d_ref's) to match the semantics of regularC++ binding object references (d_ref's), for cases in which multiple lc_d_ref's refer to an object of the same class withthe same id.196 Caché Upgrade Checklists