Caché SQL Version F.12 Release Information

Transcription

1 Caché SQL Versio F.12 Release Iformatio Versio: Caché SQL F.12 Date: October 22, 1997 Part Number IS-SQL-0-F.12A-CP-R

2 Caché SQL F.12 Release Iformatio Copyright IterSystems Corporatio 1997 All rights reserved NOTICE PROPRIETARY CONFIDENTIAL This documet cotais trade secret ad cofidetial iformatio which is the property of IterSystems Corporatio, Oe Memorial Drive, Cambridge, MA 02142, or its affiliates, ad is furished for the sole purpose of the operatio ad maiteace of the products of IterSystems Corporatio. No part of this publicatio is to be used for ay other purpose, ad this publicatio is ot to be reproduced, copied, disclosed, trasmitted, stored i a retrieval system or traslated ito ay huma or computer laguage, i ay form, by ay meas, i whole or i part, without the express prior writte coset of IterSystems Corporatio. The copyig, use ad dispositio of this documet ad the software programs described herei is prohibited except to the limited extet set forth i the stadard software licese agreemet(s) of IterSystems Corporatio coverig such programs ad related documetatio. IterSystems Corporatio makes o represetatios ad warraties cocerig such software programs other tha those set forth i such stadard software licese agreemet(s). I additio, the liability of IterSystems Corporatio for ay losses or damages relatig to or arisig out of the use of such software programs is limited i the maer set forth i such stadard software licese agreemet(s). THE FOREGOING IS A GENERAL SUMMARY OF THE RESTRICTIONS AND LIMITATIONS IMPOSED BY INTERSYSTEMS CORPORATION ON THE USE OF, AND LIABILITY ARISING FROM, ITS COMPUTER SOFTWARE. FOR COMPLETE INFORMATION REFERENCE SHOULD BE MADE TO THE STANDARD SOFTWARE LICENSE AGREEMENT(S) OF INTERSYSTEMS CORPORATION, COPIES OF WHICH WILL BE MADE AVAILABLE UPON REQUEST. IterSystems Corporatio disclaims resposibility for errors which may appear i this documet, ad it reserves the right, i its sole discretio ad without otice, to make substitutios ad modificatios i the products ad practices described i this documet. Caché, IterSystems, Caché SQL, Visual M, Caché ObjectScript, Caché Objects, DCP ISM, DTM, DT-MAX, DT-Widows, DSM, DSM DDP, ad DASL are trademarks ad M/SQL ad M/PACT are registered trademarks of IterSystems Corporatio. VAX, Alpha, OpeVMS, ad DEC are trademarks of Digital Equipmet Corporatio. Microsoft, MS-DOS, Microsoft Access, ad, Excel are registered trademarks ad Widows, Widows NT, Widows 95, Visual Basic, ad Visual C++ are trademarks of Microsoft Corporatio. For support questios about ay IterSystems products, cotact the IterSystems Worldwide Respose Ceter: Phoe: US: Europe: +44 (0) Fax: US: Europe: +44 (0) Iteret support@itersys.com FTP Site - ftp.itersys.com World Wide Web BBS: Geeral Use: +1 (617) Europe: +44 (0)

3 Table of Cotets Release Iformatio Itroducig Caché SQL Covertig Your Caché SQL Applicatios to Versio F New Features ad Ehacemets Correctios Limitatios Documetatio Notes Caché SQL Versio F.12 Release Iformatio iii

4 Table of Cotets iv Caché SQL Versio F.12 Release Iformatio

5 Release Iformatio Itroducig Caché SQL Caché SQL is the ew ame of Ope M with SQL. This ame reflects its release with Caché 2.1, IterSystems post-relatioal database. See the Caché 2.1 Release Iformatio for more iformatio o Caché. File ad Utility Names If you are familiar with previous IterSystems database products, the most obvious ew feature of this release of Caché is its ame. May files ad utility ames have bee chaged to maitai cosistecy throughout the product. Most of these chages are performed for you by the coversio process. The ame of our procedural laguage has also bee chaged to Caché ObjectScript. Caché ObjectScript is fully upward compatible with IterSystems Ope M laguage, but cotais may additioal features, icludig ew sytax for use with Caché object techology. Ope M Relatioal Server is ow called Caché SQL Server. These ame chages are reflected i all meu titles, meu optios, ad meu help. See the Addedum B of the Caché 2.1 Release Iformatio, Name Chages, for a complete list of chages. Caché SQL Versio F.12 Release Iformatio 5

6 Release Iformatio Covertig Your Caché SQL Applicatios to Versio F.12 Whe you upgrade to Caché SQL Versio F.12, you eed to perform the followig steps to covert your existig Ope M with SQL applicatios: 1. Back up your system. Oce you have coverted to the ew routie storage global structure, you caot dowgrade to earlier versios of Ope M with SQL. 2. Ru the Caché SQL coversio program i each directory/uci (except the maager s directory ad the Caché SQL commo directory). The coversio program cosists of a series of routies that update certai Caché SQL iteral structures to make them compatible with the ew versio. Caché SQL provides the Coversio Maager utility to assist you i ruig the appropriate coversio program(s). 3. After ruig the coversio program, you should recompile all Caché SQL objects i each directory/uci (except the maager s directory ad the Caché SQL commo directory). Caché SQL provides the %mcompil utility to assist you i recompilig Caché SQL objects. Coversio Maager Utility The Coversio Maager utility rus coversio routies beeath a widow-based iterface. It automates the task of covertig to a ew Caché SQL versio o a per directory basis ad allows you to selectively exclude udesired features of the target versio. The Coversio Maager also allows you to ru coversio routies multiple times ad prit reports associated with a particular coversio task. You should ormally ru the Coversio Maager i each directory/uci that you are upgradig. For complete iformatio o how to covert Caché SQL applicatios usig the Coversio Maager utility ad recompile Caché SQL objects usig the %mcompil utility, see the Ope M with SQL Database Admiistrator s Guide. Note: All Stored Procedures must be deleted from the Caché SQL Server prior to coectig from the Caché SQL Driver. 6 Caché SQL Versio F.12 Release Iformatio

7 New Features ad Ehacemets New Features ad Ehacemets Macro Compiler There is a ew etry poit, all (Namespace ALL), i the %urcomp utility. This etry poit compiles all.mac ad.int routies i all amespaces. Example >d all^%urcomp The utility prompts you for sytax checkig of the routies durig compilatio. It also prompts for a output device. If you choose a output device other tha the priciple device, the utility prits a small amout of iformatio o the priciple device to keep you up to date o the progress of the compilatios. Note: Routies i the %SYS amespace ad % routies mapped out of the %SYS amespace are ot compiled. The timestamp placed o the first lie of the.int code versios of routies by the macro preprocessor ow icludes a 4 digit value for the year. Old timestamp: New timestamp: Compiled 07/15/97 12:00PM for M/UX Compiled 15 Jul :00PM for M/UX Caché SQL provides the ability to defie empty macros ad have them expaded by the macro preprocessor. Example: #DEFINE abc _" test" #DEFINE def w!,"this is a "$$$abc w!,"this is a "$$$def expads to: w!,"this is a "_"test" w!,"this is a " Implemetatio of SQL IterSystems has implemeted additioal optimizatio for SQL queries that use multiple ORs or the IN predicate as part of the WHERE coditio. This is a cosiderable performace ehacemet. Caché SQL Versio F.12 Release Iformatio 7

8 Release Iformatio SQL Server IterSystems ow supports expressios i the INSERT VALUE-List. The followig query sytax is recogized by embedded SQL ad ay Cliet/Server applicatios that support ODBC: INSERT INTO MRP670 (MRP670, SQL_DATE, SQL_TIME, SQL_TIMESTAMP) VALUES( 6969, {d ' '}, {t '14:30:30'}, {ts ' :30:30'}) or INSERT INTO MRP670 (MRP670, SQL_DATE, SQL_TIME, SQL_TIMESTAMP) VALUES( 6969, --(*vedor(microsoft),product(odbc) d ' '*)--, --(*vedor(microsoft),product(odbc) t '14:30:30'*)--, --(*vedor(microsoft),product(odbc) ts ' :30:30'*)--) Ope M Relatioal Server is ow called Caché SQL Server. This ame chage is reflected i all meu titles, meu optios, ad meu help. Ope M Relatioal Cliet is ow called Caché SQL Driver. 8 Caché SQL Versio F.12 Release Iformatio

9 Correctios Correctios Data Dictioary IterSystems has corrected a <UNDEFINED> error compilig tables cotaiig idex maps without filig code. Queries IterSystems has corrected a problem with queries that build temporary globals. If you had DISTINCT(field) or fuctio(field) for each sort_field i the select statemet, ad you sorted by a NULL field for oe or more of the rows, the query oly retured oe row of data. IterSystems has corrected a <MAXSTRING> error whe compilig a query with a order by clause cotaiig more tha 10 fields. IterSystems has corrected a <UNDEFINED> error whe compilig a query that uses a Coditioal Map. IterSystems has corrected a problem with geerated code for multiple choice multi-lie fields usig the %EXTERNAL operator. Import/Export IterSystems has corrected a problem where geeral import was ot properly importig override ivalid coditios for map access path specificatios if the override coditio eded with "}". IterSystems has corrected a problem where geeral export/import did ot properly export a M/PACT report s data selectio if it was agaist a multiple choice field with exteral ad iteral values. SQL Cliet/Server IterSystems has added fuctioality to the Caché SQL Server for compatibility with the Caché SQL Driver. Note: All stored procedures must be deleted from the Caché SQL Server prior to coectig from the Caché SQL Driver. IterSystems has corrected a <MAXSTRING> error compilig a Stored Procedure with more tha 80 SELECT-List items. Caché SQL Versio F.12 Release Iformatio 9

10 Release Iformatio Forms IterSystems has corrected a <UNDEFINED> error compilig multirow forms cotaiig brachig fields with traslatios ad pre-field triggers with refereces to other fields. 10 Caché SQL Versio F.12 Release Iformatio

11 Limitatios Limitatios Caché SQL (Geeral) Caché SQL Developer objects (with the exceptio of forms) ca ot have foreig characters i their idetifier ames. Form ames, however, ca iclude both foreig characters ad puctuatio marks i their idetifier ames. [M/SQL C.91-01] Data Dictioary Whe ruig Caché SQL, a Base Table ca cotai a maximum of approximately 150 fields. The calculatio for a computed field ca referece a maximum of approximately 35 other fields. [M/SQL 89-12] A sigle lookup query defied i the Data Dictioary lookup specificatios should cotai o more tha 7 lookup fields ad 7 lookup display fields. From this, you should subtract oe field for each level of depedecy of the table, i.e. 6 fields for a child table, 5 for a gradchild table, etc. [M/SQL 89-12] IterSystems discourages use of the %data ad %edit arrays i SQL triggers due to the possibility of their beig NEWed withi the SQL trigger. If ecessary, use a previous trigger item to copy the values from %data ad %edit ito local variables. [M/SQL 89-12] If you chage a RowID defiitio, Caché SQL does ot automatically update the Row ID calculatio i the Data Dictioary maps. I order to force the recalculatio of the RowID, you must delete the existig RowID calculatio from every map defiitio i the table. To do this, eter each map defiitio, select RowID Calculatio, ad delete the existig Row ID calculatio by pressig the <REMOVE> key or by selectig the Delete a Etire Row optio from the horizotal meu. Oce you have deleted the existig calculatio, Caché SQL automatically geerates the ew calculatio. [M/SQL 89-12] Form Geerator Multi-row forms caot be widow-ordered. If you attempt to create a multi-row widow-ordered form, the Form Compiler issues a warig message durig compilatio, ad the form igores the widow-order list at ru time. [Ope M/SQL Versio F.6] Database fields with the data types Desigative Referece ad Multiple Choice do ot display horizotal meu optios. [Ope M/SQL Versio F.6] Caché SQL Versio F.12 Release Iformatio 11

12 Release Iformatio If you have a RowID that is based o other fields ad those based-o fields appear o a form, you must make sure that users do ot modify their values after filig a iitial value. Modifyig the values of based-o fields may cause the form to behave erratically. [Ope M/SQL Versio F.6] Field validatio code does ot act o default values for form-oly fields or o default values passed i via a default array (the 8th parameter of the M form call sytax). You are resposible for your ow validatio checkig o these default values. [Ope M/SQL Versio E.3] Brachig Fields You caot specify Coversio/Validatio code for fields of data type Brachig. The Coversio/Validatio Code optio does ot appear o the horizotal optios meu of the field defiitio. [Ope M/SQL Versio F.6] Triggers Caché SQL eforces the followig limitatios for Post-Widow triggers associated with the master widow of a multi-row form: The actio type Set Field is ot available You caot referece fields usig curly brace sytax {fieldame} i triggers of actio type M Code [Ope M/SQL Versio F.7] The Delete Row actio type is ot supported at the followig trigger locatios for multi-row forms: Pre-Widow triggers Post-Widow triggers Post-Retrieval triggers [Ope M/SQL Versio F.7] Whe usig Set Field triggers to target Desigative Display fields, you caot set the field directly. O the Set Field popup widow, you must accept the No respose to the Set the Field Directly? prompt. Attemptig to set the field directly causes the Form Compiler to geerate a warig message durig form compilatio statig that the trigger is igored. [Ope M/SQL Versio F.6] Programmed Lookups It is ot possible to defie programmed lookups for fields with data types Brachig, Desigative Display, Desigative Referece, or Multiple Choice. Selectig the Programmed Lookups optio o the horizotal optios meu of the field defiitio returs you to the mai field defiitio widow. [Ope M/SQL Versio F.6] 12 Caché SQL Versio F.12 Release Iformatio

13 Limitatios You caot referece the variables x, y or tmp i programmed lookup code. If you referece ay of these variables, your programmed lookup does ot work properly. [Ope M/SQL Versio F.6] Roll ad Scroll Mode You caot access the M/SQL System Help Meu whe ruig forms i Roll-ad-Scroll mode. Pressig the <HELP> key while i Rollad-Scroll mode causes the termial to beep. [Ope M/SQL Versio F.6] You caot see or access ay meu objects whe ruig forms i Roll-ad-Scroll mode. This icludes form meu bars ad widow meu bars as well as meu bars ad pop-up meus called by form triggers. [Ope M/SQL Versio F.6] Lookup Specificatios I the Lookup Specificatio widow (both i the Data Dictioary ad i the Form Geerator), you must ot specify multi-lie fields as a lookup fields (Fields To Lookup O) or lookup display fields (Fields To Display). [Ope M/SQL Versio F.6] Lookup boxes ca accommodate a maximum of 7 lookup display fields. If you defie more tha 7 lookup display fields i a lookup query, Caché SQL displays oly the first 7. You receive a warig message to this effect at compile time. [Ope M/SQL Versio E.5] Meu Geerator The Meu Geerator limits Meu Item ames for old-style vertical ad horizotal meus to 42 characters. [M/SQL B 90-09] M/PACT M/PACT reports caot use {fieldame} referece i pre- ad postreport triggers with actio type of M Code. [Ope M with SQL Versio F.11] Whe a M/PACT report is based o either of the followig: Query View that is itself based o a query it caot use the Elimiate Cartesia Product? optio. I this case, the Elimiate Cartesia Product? field o the Report Defiitio Advaced Optios widow is set to No, ad you caot access it. [Ope M/SQL Versio F.6] Caché SQL Versio F.12 Release Iformatio 13

14 Release Iformatio I a report based o a query data source, oce the query is imported ito the report defiitio, it is ot possible to modify the text of the origial query ad reimport it or otherwise update the query withi the report. [Ope M/SQL Versio E.5] M/PACT places a limitatio o the umber of data colums that you ca iclude i a report defiitio. If you exceed this limitatio, compilatio of the report defiitio fails due to a <MAXSTRING> error. The umber of data colums to which you are limited varies, depedig o the complexity of the formattig attributes associated with your data colums. Formattig attributes iclude Width, Aligmet, Value Formattig, ad eve attributes associated with the field defiitio, such as Iteral-to-Exteral Coversio code. If you do ot associate ay formattig attributes with the data colums, M/PACT allows a maximum of approximately 16 data colums i a report defiitio. To the extet that you do defie formattig attributes, that umber decreases. [Ope M/SQL Versio D ] Implemetatio of SQL The LIKE predicate yields upredictable results whe it is used i a expressio that refereces a field as the <match value> operator (value o the left side of the LIKE predicate), ad the field uses the ALPHAUP collatio fuctio. [Ope M/SQL Versio F.7] The INTO clause caot recover fields from a view ito a local array. [Ope M/SQL Versio D ] The Iteractive Query facility does ot support the use of the INTO clause. [Ope M/SQL Versio D ] 14 Caché SQL Versio F.12 Release Iformatio

15 Documetatio Notes Documetatio Notes Set Field Triggers That Target Multi-Lie Fields Whe defiig a Set Field trigger that targets a multi-lie field, you ca set the trigger to remove all istaces of the multi-lie field, as follows: [Ope M/SQL Versio F.6] Whe you specify the field ame i the Trigger Defiitio widow, specify just the field ame, ad do ot specify a lie umber i paretheses. I the Set Field popup widow, leave everythig blak. You caot use the Set Field trigger actio to set the lie couter of a multi-lie field. Do ot attempt to set the lie couter by specifyig FieldName(0) i the Trigger Defiitio widow. [Ope M/SQL Versio F.6] Usig Percet Variables i Form Triggers for Multi-Row Forms I multi-row forms, you ca oly referece row-specific percet variables i Post-Field triggers. The row-specific percet variables are: {%filetype} {%presave} {%savedata} {%retur_filetype} {%retur_presave} {%retur_savedata} These percet variables hold iformatio that is specific to oe data row, ad therefore, must be used i referece to a specific row. I sigle-row forms (where there is oly oe row), you ca also referece these percet variables i Post-Widow ad Post-Form triggers. Field Skippig Rows i Multi-Row Forms If a user exits a row i a multi-row form usig either the <DOWN ARROW> or <NEXT SCREEN> keystroke ad the field to be laded o is defied to be skipped, the field is skipped as if the user had pressed <RETURN> while i it. [Ope M/SQL Versio E.4] If a row is exited with a UP keystroke (e.g., <UP ARROW> or <PREVIOUS SCREEN>) ad the field to be laded o is to be skipped, the field is skipped as if the user had pressed the <LEFT ARROW> key while i it. [Ope M/SQL Versio E.4] Caché SQL Versio F.12 Release Iformatio 15

16 Release Iformatio Available Documetatio Caché SQL The documetatio set for IterSystems Caché SQL relatioal database product icludes the followig mauals: This Caché SQL Versio F.12 Release Iformatio; Revisio Date: August, Ope M with SQL Versio F.11 Release Iformatio; Revisio Date: July, Ope M/SQL Developer Guide Versio F.6 & F.7; Revisio Date: September 11, Ope M with SQL Database Admiistrator s Guide Versio F.9, F.10; Revisio Date: December 9, User Iterface Programmig Guide Versio F.4; Revisio Date: October 6, Ope M with SQL Data Dictioary Guide Versio F.10; Revisio Date: April 2, Ope M/SQL M/PACT (icludes M/PACT Addedum) Versio B; Revisio Date: July 2, Caché SQL Server If you pla to use Caché SQL Server, you also eed the followig documetatio: Caché SQL Driver User s Guide Versio 2.2; Revisio Date: September, Ope M/SQL Server Programmig Guide Versio E.3; Revisio Date: May 5, Available o request. Ope M Relatioal Server Maager s Guide Versio F.10; Revisio Date: December 9, Caché SQL Versio F.12 Release Iformatio