13.07.2015 Views

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Caché</strong> 2009.1 <strong>Upgrade</strong> ChecklistPrior to this version, it would simply give a syntax error at compile time. Now an error will be returned when the query isprepared/compiled that explains this is not supported. The SQLCODE value for this error -144, “Sub-queries are notallowed in insert statements”.6.2.8.17 Return BINARY Type For SUBSTRING()When using SUBSTRING() with an argument of type LONGVARBINARY, the result returned is now of type BINARY(%Library.Binary), not VARCHAR (%Library.String).6.2.8.18 Specifying The Collation For A Field In DDLWhen a the collation of a field is specified via a DDL CREATE TABLE or ALTER TABLE statement, an error will nowbe returned if the collation specified is not a collation support by <strong>Caché</strong>. In previous versions, an indicating an unsupportedcollation name would be returned during CREATE TABLE, but not during ALTER TABLE. Now, both CREATE TABLEand ALTER TABLE will return a meaningful error message.Also, when the class is defined and a collation is specified via DDL, the collation value in the collation property parameterwill be forced to all uppercase.6.2.8.19 No Collation Specified Defaults to EXACTSubscript information for collated fields is now reported as %EXACT when no collation (or so-called EXACT collation)is applied to a property.6.2.8.20 Return OREFs Instead Of OIDs In SQL QueriesIn prior versions, when embedded and dynamic SQL queries returned external streams as part of their results, the referencesto the streams were returned as OIDs (object ids; %Library.ObjectIdentity). Beginning in this version, the stream referenceswill be returned as OREFs (object references; %Library.ObjectHandle).WARNING!Existing applications returning external streams as results must be modified to use the new type.6.2.8.21 Trailing Delimiter Modified After SQL UPDATEA change has been made to the SQL data filer for UPDATE to prevent a trailing delimiter value from being added to aglobal node. This happens if %CacheSQLStorage is used with delimited identifiers for the node. For example suppose thenode looks like^Patient({ID},10) = {Name} ^ {Age}After an SQL UPDATE, in some cases, the node would be changed to look like^Patient({ID},10) = {Name} ^ {Age} ^While this data is still valid, it may interfere with applications that look at the global data directly. SQL adds the trailingdelimiter if the data in the table beyond the trailing delimiter is defined.6.2.9 SQL Gateway Changes6.2.9.1 Use %Library.Double For Linked Tables<strong>Caché</strong> now represents floating-point values in linked tables by %Library.Double instead of %Library.Float.152 <strong>Caché</strong> <strong>Upgrade</strong> <strong>Checklists</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!