Caché Upgrade Checklists - InterSystems Documentation

DevelopersClass NameConfig.ECPConfig.ECPServersConfig.ETHServersConfig.IOConfig.JournalConfig.LATConfig.MagTapesConfig.MapConfig.MiscellaneousConfig.MonitorConfig.NamespacesConfig.NetConfig.SQLConfig.SqlSysDatatypesConfig.SqlUserDatatypesConfig.StartupConfig.TelnetConfig.UDPServersMethod Name(s)LoadLoadLoadLoadLoadLoadLoadMoveToActiveLoadLoadLoadLoadLoadLoadLoadLoadLoadLoad5.2.5.8 Method DisplacementsThe following methods have been removed from one class and added to another:• Method: KPI – from %BI.Soap to %BI.Util• Method: Pivot –: from %BI.Soap to %BI.Util5.2.5.9 DBTIME Implementation ChangedThe DBTIME parameter was first introduced in version 2008.2. When set to 1, it caused an index to be defined in the classon a property that was, by default, set to an incremented global on each insert and update; but the index entry for an objectwas not updated for deletes.Beginning with this version, DBTIME no longer generates an index definition and property definition. A global,^OBJ.DBTIME, is set for each insert, update and delete. The first subscript is the incremented global counter -^OBJ.DBTIME; the second is the class name of the object being filed; and the third is the ID of the object. The value ofthe global node for each filing event is the type of filing - 0 for update, 1 for insert and 2 for delete. This structure iscumulative. It is used to support various features in Cache and it can be used by user applications for any purpose. Deletingentries from ^OBJ.DBTIME is not automatic and must be done by the user.5.2.5.10 Permit Insert Of Trailing Objects In CollectionsThe SetAt method of a list collection allows the caller to specify an element value and a key. In prior releases, if the elementat the key position was not already defined, then the attempt would fail.Caché Upgrade Checklists 119