Caché Upgrade Checklists - InterSystems Documentation

Developers9.2.3.8 Statement ChangesThe following is a short list of changes to statement parsing. Please refer to the SQL Reference manual for further information.• The INTO keyword is now optional on an INSERT statement• The UPDATE and DELETE statements now allow a new FROM clause to support multi-table selection criteria• The FROM keyword is now optional in a DELETE statement9.2.3.9 Operator / Predicate ChangesThe following are new in version 2007.1:• The LIKE predicate supports letter case collation• %CONTAINSTERM has been added as a new comparison operator9.2.3.10 New Comment SyntaxCaché SQL now supports multiline comments with the same /* ... */ syntax used by Caché Objectscript.9.2.4 Changes to %Text Class StemmingThe %Text.English class uses the Porter stemmer, which is a widely used published algorithm for stemming English words.The published algorithm includes an amended method for stemming “-ed” word endings that has been used in all versionsof the %Text.English class.In this version of Caché, the algorithm has been changed to restore the behavior of the originally published algorithm,because the amended algorithm does an inferior job on most words ending in “-ed”. This change affects what terms gointo an index based on the %Text.English class, so any index that is not rebuilt across versions may experience slight differenceswith respect to text predicates on words ending in “-ed”.Important:It is recommended that you rebuild %Text.English text indices that were created on prior versions of Caché.Otherwise, a word that could end in “-ed” might fail to match a different form of the word already in theindex.9.2.5 Changes to CallinIn this release of Caché, CALLIN no longer supports msql* functions. These must be changed to Caché SQL.9.2.6 Corrections9.2.6.1 String TruncationAn error has been fixed that under some circumstances caused Caché to ignore maximum string length settings. This allowedstrings whose length exceeded the maximum to be accepted instead of being detected as being too long. Subsequent use,for example, when the value was passed to a stored procedure or persisted, would correctly truncate the value. Values arenow processed consistently for both the initial and subsequent uses.Caché Upgrade Checklists 217