Caché Upgrade Checklists - InterSystems Documentation

Developers11.2.8.3 SQL Passwords Are Case-SensitiveIn Version 5.1, for security reasons, SQL uses the same password mechanisms as Caché. One consequence of this is thatSQL passwords are now case-sensitive. Previously, they were not.11.2.8.4 Table Ownership Interaction With $USERNAMEThis means that tables created through the use of DDL will have as owner the value of $USERNAME at the time they werecreated. When creating a class or table by any other means, the class's OWNER keyword is not defined unless the developerexplicitly defines it. When a class is compiled that projects a table and the class's OWNER keyword is NULL, the table'sowner is set to _SYSTEM.This interpretation is the same as in previous versions. What has changed is that there is no default to an OWNER of_SYSTEM when creating tables through DDL in 5.1.11.2.8.5 Delimited Identifiers Are The DefaultCaché version 5.1 installs with the value for “Support Delimited Identifiers” as true. This means that a double-quoted string(“My String”) is considered a delimited identifier within an SQL statement. Prior versions of Caché had this parameter setto false: a double-quoted string was treated as a string constant or literal string. The value of this parameter can be changedvia the System Management Portal at [Home] > [Configuration] > [Advanced Settings].11.2.8.6 %msql EliminatedThis variable was used in Caché ObjectScript to specify a valid user name for SQL access from embedded SQL. A validuser name was one that was registered in the User Table.In Caché 5.1, the SQL username is now extracted from the $USERNAME special variable which is set when the user isauthenticated.11.2.8.7 Cached Query ChangesCached Query Interaction With Read-Only DatabasesIn Caché 5.1, SQL queries that require Cached Queries will not work against read-only databases unless the ^mcq globalis mapped to a database mounted as read-write. An example of this interaction is attempting to create a table in a read-onlydatabase using SQL DDL.Cached Query Changes Are Not JournaledIn version 5.1, when cached queries are modified, the changes are no longer journaled. This prevents changes to cachedqueries inside a transaction from being written to the journal. Thus, shadowing will not apply cached query changes acrosssystems.Purging Cached Queries Is ImmediateCaché 5.1 no longer supports the concept of purging cached queries after N days, where N is a number of days defined inthe configuration setting. When an application calls Purge(), it will purge all cached queries.Cached Queries On Read-Only DatabasesThis version of Caché permits applications to Prepare and Execute Dynamic SQL cached queries that do SELECTs againstthe table of the database.Note:Any attempt by the application to purge such queries will result in a error. Purging cached queriesrequires write access to the database they are associated with.Caché Upgrade Checklists 259