4D v14. Upgrade Windows /OS X. 4D D SAS. All Rights Reserved.

Transcription

1 4D v14 Upgrade Windows /OS X 4D D SAS. All Rights Reserved.

2 4D v14 - Upgrade Windows and OS X Versions Copyright D SAS. All Rights Reserved. The software described in this manual is governed by the grant of license provided in this package. The software and the manual are copyrighted and may not be reproduced in whole or in part except for the personal licensee s use and solely in accordance with the contractual terms. This includes copying the electronic media, archiving, or using the software in any manner other than that provided for in the Software license Agreement. 4D, 4D Write, 4D View, 4D Server and the 4D logos are registered trademarks of 4D SAS. Windows, Windows XP, Windows 7, Windows Vista and Microsoft are registered trademarks of Microsoft Corporation. Apple, Macintosh, imac, Mac OS X and QuickTime are trademarks or registered trademarks of Apple Computer Inc. Mac2Win Software Copyright is a product of Altura Software, Inc. ICU Copyright International Business Machines Corporation and others. All rights reserved. ACROBAT Copyright , Secret Commercial Adobe Systems Inc. All rights reserved. ACROBAT is a registered trademark of Adobe Systems Inc. This product includes software developed by the Apache Software Foundation ( 4th Dimension includes cryptographic software written by Eric Young (eay@cryptsoft.com) 4th Dimension includes software written by Tim Hudson (tjh@cryptsoft.com). Spellchecker Copyright SYNAPSE Développement, Toulouse, France, All other referenced trade names are trademarks, registered trademarks, or copyrights of their respective holders. IMPORTANT LICENSE INFORMATION Use of this software is subject to its license agreement included with the software. Please read the License Agreement carefully before using the software.

3 Contents Chapter 1 Welcome Conversion of earlier databases Databases in versions < Databases in versions 11 or Databases in version Components in versions 11, 12 or Support for 64-bit plug-ins under Windows Support of IPv Functional compatibility Obsolete functions Removed functions Minimum configuration Chapter 2 Development workshop New data journaling "Include in Log File" Option Default primary key field Primary key error window Primary key manager Viewing the primary key in the MSC Debugging help Ignoring errors Real Time Monitor Starting log files D components Application builder Automating updating of server applications New automatic updating procedure for client applications.. 36 Update log New "AutoUpdate" XML keys (Windows) New "SignApplication" XML keys D v14 Upgrade 3

4 Contents New query editor Access to editor Editor menus Building queries Query by formula Support of Mecab (Japanese version) Chapter 3 Forms and objects Placeholder text Combo boxes Automatic insertion of values Excluded List Mouseover of values under OS X Multi-style areas Mouseover Context Menu New tags Allowing color and font pickers Hierarchical lists List boxes New Wordwrap property New graphic column properties Priority of styles and colors Support of standard actions New properties Choice lists associated with objects Pop-up menus and combo boxes associated with fields and variables Storage of references Rotation of text Objects eligible to rotate Setting the rotation Rotation of fields and variables Modifying an object with rotation Memorization of window geometry Save Geometry option Save Value option Storage and use of information Examples Spell checking Choice of dictionary Checking process D v14 Upgrade

5 Contents Web Areas Accessing 4D methods Access to Web inspector Chapter 4 SQL Support for SQL views CREATE VIEW DROP VIEW New system tables on the views New options using ALTER TABLE ALTER TABLE New columns for system tables Support of date and time constants Chapter 5 4D Mobile D Mobile Architecture Step-by-step example Creating and configuring the 4D database Creating the Wakanda application Displaying 4D data using a Wakanda widget Creating and calling a 4D method Configuring the 4D database Starting Wakanda REST services Control of REST accesses On REST Authentication Setting 4D objects exposed in REST Explorer Configuration of Wakanda application Execution of the mergeoutsidecatalog() method Calling 4D tables Using relations Calling 4D methods openremotestore() and addremotestore() About 4D Mobile application security Chapter 6 Language D Environment New commands Get last update log path RESTART 4D SET UPDATE FOLDER Modified commands D v14 Upgrade 5

6 Contents GET MEMORY STATISTICS SET DATABASE PARAMETER, Get database parameter Version type Arrays ARRAY BLOB ARRAY OBJECT ARRAY TIME ARRAY TO LIST LIST TO ARRAY SELECTION TO ARRAY, SELECTION RANGE TO ARRAY Backup INTEGRATE MIRROR LOG FILE BLOB BLOB TO VARIABLE, VARIABLE TO BLOB Compiler C_OBJECT Database methods On Host Database Event On REST Authentication Date and Time Conversion of JavaScript dates Time Display of null dates Design Object Access FORM GET NAMES METHOD GET CODE METHOD SET ATTRIBUTE METHOD SET CODE Drag and Drop SET DRAG ICON Form Events Form event Forms Current form name FORM LOAD FORM UNLOAD Graphs GRAPH GRAPH SETTINGS GRAPH TABLE Hierarchical Lists Association with form objects HTTP Client HTTP Get HTTP Get certificates folder D v14 Upgrade

7 Contents HTTP Request HTTP SET CERTIFICATES FOLDER JSON Introduction to JSON JSON Parse JSON PARSE ARRAY JSON Stringify JSON Stringify array JSON TO SELECTION Selection to JSON List Box LISTBOX DUPLICATE COLUMN LISTBOX Get array LISTBOX GET OBJECTS LISTBOX Get row color LISTBOX Get row font style LISTBOX MOVE COLUMN LISTBOX SET ARRAY LISTBOX SET ROW COLOR LISTBOX SET ROW FONT STYLE Messages DISPLAY NOTIFICATION Object Properties Objects (Forms) New commands GET STYLE SHEET INFO LIST OF STYLE SHEETS OBJECT Get action OBJECT Get border style OBJECT Get context menu OBJECT Get data source OBJECT GET EVENTS OBJECT Get indicator type OBJECT Get list reference OBJECT GET MAXIMUM VALUE OBJECT GET MINIMUM VALUE OBJECT Get multiline OBJECT Get placeholder OBJECT GET PRINT VARIABLE FRAME OBJECT Get style sheet OBJECT Get text orientation OBJECT Get three states checkbox OBJECT Get type OBJECT Is styled text OBJECT SET ACTION D v14 Upgrade 7

8 Contents OBJECT SET BORDER STYLE OBJECT SET CONTEXT MENU OBJECT SET COORDINATES OBJECT SET DATA SOURCE OBJECT SET EVENTS OBJECT SET INDICATOR TYPE OBJECT SET LIST BY REFERENCE OBJECT SET PLACEHOLDER OBJECT SET PRINT VARIABLE FRAME OBJECT SET MAXIMUM VALUE OBJECT SET MINIMUM VALUE OBJECT SET MULTILINE OBJECT SET STYLE SHEET OBJECT SET TEXT ORIENTATION OBJECT SET THREE STATES CHECKBOX Modified commands OBJECT Get choice list name OBJECT Get list name OBJECT GET RGB COLORS OBJECT SET CHOICE LIST NAME OBJECT SET FONT OBJECT SET LIST BY NAME OBJECT SET RGB COLORS Interaction of generic commands with multi-style areas Objects (Language) Structure of 4D objects OB Copy OB Is defined OB Is empty OB Get OB GET ARRAY OB GET PROPERTY NAMES OB Get type OB REMOVE OB SET OB SET ARRAY OB SET NULL Picture operators "&" operator (exclusive superimposition) " " operator (inclusive superimposition) Printing OPEN PRINTING FORM Processes Execute on server D v14 Upgrade

9 Contents Quick Report QR REPORT QR SET DESTINATION Spell Checker SPELL CHECK TEXT SPELL GET DICTIONARY LIST SPELL SET CURRENT DICTIONARY String String Structure Access PAUSE INDEXES RESUME INDEXES Styled Text New commands ST COMPUTE EXPRESSIONS ST FREEZE EXPRESSIONS ST Get content type ST Get expression ST GET OPTIONS ST GET URL ST INSERT EXPRESSION ST INSERT URL ST SET OPTIONS Modified command ST Get plain text Automatic normalization of line endings Using constants for selection limits Renamed commands System Documents COPY DOCUMENT Document to text TEXT TO DOCUMENT System Environment Modified commands FONT LIST Font name Font number New commands OPEN COLOR PICKER OPEN FONT PICKER SET RECENT FONTS Tools Generate digest GET ACTIVITY SNAPSHOT D v14 Upgrade 9

10 Contents User Interface SHOW TOOL BAR, HIDE TOOL BAR Tool bar height Users and Groups Validate password Web Area WA Evaluate JavaScript WA EXECUTE JAVASCRIPT FUNCTION WA SET PREFERENCE Web Server WEB SEND TEXT Web Services (Client) WEB SERVICE CALL WEB SERVICE Get info Windows Window types (OS X) Renamed constant D Internet Commands Unicode by default SMTP_Attachment SMTP_Body SMTP_MessageID SMTP_QuickSend SMTP_Subject D Pack Commands removed from 4D Pack TimePicker Widget Clock Digital clock TimePicker DISPLAY SECOND HAND TimePicker LCD DISPLAY AMPM TimePicker LCD DISPLAY SECONDS TimePicker LCD SET COLOR TimePicker LCD SET MODE D v14 Upgrade

11 1 Welcome Welcome to 4D v14. This new version is characterized by major evolutions in its architecture as well as numerous additions to enrich the interfaces of your applications, while still maintaining maximum compatibility with existing databases. Modernization of 4D core: internally, rewriting of code that used the former carbon libraries now allows 4D v14 to overcome performance limitations imposed by these libraries; in return, older-generation technologies such as QuickTime, 4D Chart or the Pict picture format are no longer supported. Forms in 4D v14 have many new features in particular concerning list objects (list boxes, hierarchical lists, combo boxes, etc.), Web areas (new JavaScript bridges, debugger) and also text areas (rotation of static text, extension of styled text function). The development workshop has also been enhanced by simplifying the procedure for updating versions, new query dialog boxes, extended debugging help, and the new On Host Database Event database method. Specific functions are implemented at the core of 4D to let Wakanda applications make direct use of data in 4D databases. And finally, 4D s programming language has been enriched with numerous new commands, in particular to allow greater control over object properties; it also welcomes a new data type: objects (see the C_OBJECT command) as well as "JSON" type data (new theme). 4D v14 Upgrade 11

12 Chapter 1 Welcome Conversion of earlier databases Databases created with versions 11.x, 12.x and 13.x of 4D or 4D Server are compatible with 4D version 14 (structure and data files). Database files for versions earlier than version 11 must be converted using a wizard and can no longer be opened with their original version. Database files in version 11 or 12 are converted directly into version 14 and can no longer be opened with their original version. Structure files in version 13 are converted directly into version 14 and can no longer be opened with their original version. However, data files in version 13 can be opened in version 14 without conversion and can still be opened again in version 13. Note: You can convert any interpreted structure file. The file can contain compiled code; in this case, you must compile the database again after conversion. Note: If the database that you are converting is missing primary keys, the primary key error window will appear. This is covered in the New data journaling paragraph on page 21. Databases in versions < 11 Structural changes made at the 4D database engine level require indepth conversion of both the structure and data for databases prior to version 11. This conversion is performed using a specific wizard. For more information, refer to the 4D v11 SQL Upgrade and Conversion to 4D v11 SQL manuals available for download here: D v14 Upgrade

13 Conversion of earlier databases Databases in versions 11 or12 Version 11 or version 12 databases are converted directly when you open their structure file with 4D v14. Two successive warnings let you know that the files are being converted and that you can no longer open them using an earlier version: Note that when you convert a data file, its indexes are rebuilt. Databases in version 13 A database from version 13 is converted directly when you open it with 4D v14. A warning dialog box lets you know that the structure file is going to be converted and that you can no longer open it with an earlier version: Data files, however, are opened without conversion so they can still be opened again in version 13. 4D v14 Upgrade 13

14 Chapter 1 Welcome Components in versions 11, 12 or 13 4D v14 can open v13, v12 or v11 components (compiled or interpreted) directly without conversion or displaying confirmation dialog boxes. Remember that components are always opened in readonly. You do not need to recompile components but conversion to v14 is only possible for.4db files and not.4dc ones. Support for 64-bit plug-ins under Windows In v14, 4D plug-ins are available in 64-bit Windows version. This way you can take advantage of the 64-bit architecture in a configuration using the 64-bit Windows version of 4D Server. 64-bit versions are included in the plug-in bundles. No specific installation is required. The following plug-ins are available in a 64-bit Windows version: 64-bit plug-ins in Notes v14 4D Write - 4D View - 4D Internet Commands 4D Pack The 4D Internet Commands v14 plug-in also includes new features. For more information, refer to the 4D Internet Commands paragraph on page 323 Modifications were made to the 4D Pack plug-in in v14. For more information, refer to the 4D Pack paragraph on page 327 4D ODBC Pro - 4D For OCI You must install the 64-bit OCI before the 64-bit 4D For OCI plug-in. You can get this version of the OCI from Oracle, Inc. Note: The functioning of 32-bit and 64-bit plug-ins is identical. However, note that the Open external window command cannot be used on a 64- bit 4D Server. 14 4D v14 Upgrade

15 Support of IPv6 Support of IPv6 4D v14 supports IPv6 address notation. This new feature concerns integrated servers of 4D v14, i.e.: the Web server as well as the SOAP server, the SQL server. Note For more information about IPv6, refer to the following specification: RFC Support of IPv6 is transparent for users and for 4D developers: the program accepts either IPv6 or IPv4 connections indiscriminately when the listening "IP address" of the server is set to All. However, you should pay attention to the following points: Indication of port numbers Since IPv6 notation uses colons (:), adding port numbers may lead to some confusion, for example: 2001:0DB8::85a3:0:ac1f:8001 // IPv6 address 2001:0DB8::85a3:0:ac1f:8001:8081 // IPv6 address with port 8081 To avoid this confusion, we recommend using the [ ] notation whenever you combine an IPv6 address with a port number, for instance: [2001:0DB8::85a3:0:ac1f:8001]:8081 //IPv6 address with port 8081 No longer any warning when TCP port is occupied Unlike previous versions of 4D, when the server is set to respond on "all" IP addresses with 4D v14, if the TCP port is being used by another application, this is no longer indicated when the server is started. In fact, 4D server does not detect any error in this case because the port remains free on the IPv6 address. However, it is not possible to access it using the IPv4 address of the machine, nor by means of the local address: If your 4D server does not seem to be responding on the port defined, you can test the address [::1] on the server machine (equivalent to for IPv6, add :portnum to test another port number). If 4D responds, it is likely that another application is using the port in IPv4. 4D v14 Upgrade 15

16 Chapter 1 Welcome Functional compatibility This section describes the new features of 4D v14 that could modify the functioning of applications converted from previous versions. Obsolete functions Pictures in PICT format The following functions are still supported in 4D v14 but they are now obsolete and their use is not recommended. The PICT format will not be supported in the next major releases of 4D and you must no longer use it in 4D v14. The AP Is Picture deprecated function, provided via 4D Pack beginning with version 13.2, is intended to help you migrate your applications. Note: The Mac "PICT" format has already been deprecated by Apple since several prior Mac OS versions (see the description of PICT format on Wikipedia). QuickTime Support for the picture codecs related to QuickTime is now obsolete. By default, the use of QuickTime is disabled in 4D v14. However for compatibility reasons, you can enable it using the new QuickTime support option of the SET DATABASE PARAMETER, Get database parameter commands. Dynamic assignment of variables received through HTTP In previous versions of 4D, the Web server automatically recopied the value of variables sent through a Web form or a URL into 4D variables when they had the same name. For reasons of optimization and control, this principle is not maintained starting with 4D v14: the value of Web variables are no longer automatically assigned to the 4D variables. To recover variables sent using a POST or a GET, you must use the WEB GET VARIABLES command exclusively. To recover the posted files, you must use the WEB GET BODY PART/WEB Get body part count commands. Note: Dynamic assignment is also disabled by default in 4D databases created beginning with version D v14 Upgrade

17 Functional compatibility However, for compatibility, this mechanism is maintained by default in databases created with a version of 4D earlier than In this case, you can disable it using the Automatic variable assignment compatibility option: Since this mechanism is obsolete, we strongly recommend that you uncheck this option in your converted databases (and adapt your code if necessary) so as to facilitate future evolutions. Query by formula Font numbers Removed functions Discontinuation of 4D Chart The query by formula editor has been merged with the standard query editor in 4D v14 (see the New query editor paragraph on page 42). The menu commands associated with it have been removed from the interface. Using QuickDraw ID numbers to designate fonts is obsolete and must no longer be used. The Font name and Font number commands are kept in 4D v14 for compatibility but will be removed in subsequent versions. The OBJECT SET FONT command now only accepts font names. As announced at the release of 4D version 13, certain obsolete functions have been removed from the 4D product line starting with 4D v14. The 4D Chart plug-in is no longer provided in version 14 and its development and maintenance have been permanently discontinued. 4D commands in the "Graphs" theme only work with the SVG syntax and the GRAPH TABLE command has been removed. 4D v14 Upgrade 17

18 Chapter 1 Welcome Tool bar in Application mode "Cordial" spell check The automatic tool bar that was available when switching to the Application mode has been removed. In 4D v14, the SHOW TOOL BAR, HIDE TOOL BAR commands are disabled and the Tool bar height command always returns 0 in Application mode. The "Display toolbar" option has been removed from the Interface page of the Database Settings. Cordial dictionaries are no longer supported in 4D v14. Only Hunspell dictionaries (as well as the native dictionary under OS X) can be used. For more information, refer to the Spell checking paragraph on page 84. & and picture operators The & and picture operators that performed XOR and OR operations (monochrome pictures) are no longer supported. The functioning of these operators in 4D v14 is new (see the Picture operators paragraph on page 273). Picture library editor The Picture library s bitmap mode editor has been removed in 4D v14. Only the display of pictures, along with the sorting, importing and splitting functions are maintained in the Tool box. Windows in noncompositing mode (OS X) The compositing mode is now used systematically for all windows created by 4D v14 under OS X. In previous versions of 4D, it was possible to create windows using a former internal management mode (based on QuickDraw). This mode is now abandoned. Thanks to compositing mode, 4D windows have new behavior and functions under OS X: animation when windows are resized windows can be resized using any wall and there is no longer a resize box in the bottom right of the windows compatibility with HiDPI screen mode (or "Retina" mode), "full screen" mode with auto-hide of main menu bar (beginning with OS X 10.7) (see the Full screen button paragraph on page 322). 18 4D v14 Upgrade

19 Functional compatibility supports for the DISPLAY NOTIFICATION command under OS X (beginning with OS X 10.8). Note: Plug-ins requiring QuickDraw must be adapted in order to be compatible with compositing mode. To ensure compatibility with plug-ins that still require QuickDraw, an emulation layer was implemented. For more information, please contact 4D technical support. Text rendering (Mac OS) In accordance with Apple's recommendations (abandoning of obsolete QD/MLTE frameworks and generalization of the use of CoreText), we updated and unified the frameworks used for text rendering in 4D under OS X beginning in version Despite our efforts to limit its impact, using the new CoreText framework may cause slight variations in the rendering of text areas under OS X for converted applications, particularly as concerns line spacing. These variations may make it necessary to resize certain form objects during conversion. 4D Pack Option+F shortcut (OS X) Alt+click shortcut for close box (Windows) Several commands found in previous versions of 4D Pack were removed from 4D Pack v14. These command are detailed in the Commands removed from 4D Pack paragraph on page 328. The Option+F shortcut, which let you "force" the switch from Application to Design mode on OS X, is removed in 4D v14. It is up to the developer to add a menu command associated with the "Return to Design mode" standard action and a custom shortcut in order to manage this operation. Note that the Option+Shift+right click shortcut can still be used to access the debug menu. The Alt+click shortcut on the close box of a window under Windows, used to close all the windows of the Design mode, is removed in 4D v14. This was a non-standard shortcut. You can use the standard shortcut for closing all windows under Windows: Ctrl+Alt+W. "Automatic Transactions during Data Entry" compatibility option This former compatibility option is no longer supported in recent versions of 4D and has been removed from the "Compatibility" page of the Database Settings in 4D 14. 4D v14 Upgrade 19

20 Chapter 1 Welcome Minimum configuration 4D version 14 product line applications require the following minimum configurations: Windows OS X Processor Intel Core Duo Intel Core 2 Duo System Windows 7 and higher OS X 10.7 (Lion) and higher RAM memory 4 GB (8 GB recommended for 64-bit 4D Server) 20 4D v14 Upgrade

21 2 Development workshop In 4D v14, many development workshop functions have been redesigned and extended for the benefit of both 4D developers and their users: On the developer side, modifications and improvements are made to functions for data journaling and maintenance, as well as debugging, component development and deployment of applications. On the user side, 4D v14 provides a new query and query by formula editor. Note that many new features specifically concern form objects. These new features are detailed in chapter 3, Forms and objects page 51. New data journaling In 4D v14, mechanisms for generating and using the log file of the data (.journal file) have been modified. These modifications bring the following benefits: allows you to set up a secured architecture using cascading backup mirrors (mirrors of mirrors), lets you choose the tables whose data must be journaled, makes the procedure for integrating a log file less linear and therefore more resistant. For example, a read error in the file concerning a recorded operation will no longer prevent the global integration of the log file (using the MSC). To do this, new principles are implemented in 4D v14: It is mandatory that each table whose data is journaled contains a primary key. 4D v14 Upgrade 21

22 Chapter 2 Development workshop You must indicate each table whose data must be journaled by means of a new option. These new rules apply to databases created with 4D v14 as well as to converted databases. They involve modifications in the Structure editor as well as new options in SQL language commands of 4D. The INTEGRATE MIRROR LOG FILE command accepts a new parameter used to manage mechanisms for mirror databases. A new assistant is provided in 4D v14 to accompany the updating of tables that do not have primary keys. The principles of how this assistant works are described in the Primary key manager paragraph on page 27. Note This assistant is also provided as a 4D v13 component so that you can prepare 4D databases to migrate to v14. "Include in Log File" Option The new Include in Log File option is available in the table Inspector of the Structure editor: New option By default, this option is checked for all new tables created in 4D v14 and for all tables in converted databases. Check this option in order for operations performed on the table s data to be included in the database log file (when it is generated). This option must generally be checked for most tables. 22 4D v14 Upgrade

23 New data journaling However, for optimization purposes, you can uncheck it, for example for temporary tables or tables used for importing data. Note This option is grayed out when the table does not have a primary key. It is important to note that this option only indicates that the table s data must be journaled if the database uses a log file; it does not enable the journaling procedure itself at the database level. Warning messages 4D displays a warning icon to the right of the Include in Log File option. As long as this icon is shown, journaling is not yet enabled. You can place your mouse over this icon to find out the cause for the warning: The following messages may be shown: Message Cause Correction needed Waiting to create a primary key Waiting for primary key values to be fixed Waiting to enable journaling at the database level Impossible to journal operations if the table does not have a primary key (new rule in 4D v14) Primary key values have been verified and include anomalies The global option for enabling journaling is not checked Create a primary key in the table using SQL or the context menu of the table Remove any duplicate or null values in the records for the field (or use another primary key) Check the Use Log File option on the Backup/Configuration page of the Database Settings Default primary key field In 4D v14, every new table created in the database contains a primary key by default: 4D v14 Upgrade 23

24 Chapter 2 Development workshop This field, named "ID" by default, is of the Longint type, and has, in particular, the following attributes: Unique, Reject NULL value input, Autoincrement, Automatic index Note In the Preferences of the 4D application, you can modify the name and type of the primary keys that are created by default. For more information, refer to the "Primary Key" preferences paragraph on page 24. You can use this field as is, or change its name and/or its properties if you want (for example, you may want to use an UUID field). You can also delete it if you want to use another field (or fields) as primary key(s). However, it is strongly recommended to keep at least one primary key in each 4D table. Note A primary key is used to uniquely identify each record in a table. It may consist of one or more fields. For more information about creating primary keys, refer to the "Table properties" section of the 4D Design Reference manual. Note Default primary keys are not added to tables that are created using the SQL CREATE TABLE command, or tables that are imported into the database. "Primary Key" preferences Two new options in the preferences can modify the default name and type of the primary key fields that are added automatically by 4D when new tables are created or by means of the Primary key manager. 24 4D v14 Upgrade

25 New data journaling These options are available on the "Structure" page of the 4D Preferences: New options The following options are available: Name ("ID" by default): Sets the default name of primary key fields. You can use any name you want, as long as it respects the naming rules for standard 4D tables. Type (Longint by default): Sets the default type of primary key fields. You can choose the UUID type. In this case, the primary key fields created by default are of the Alpha type and have the "UUID format" and "Auto UUID" properties checked. Primary key error window In 4D v14, the use of a log file requires all the journaled tables to have a valid primary key. An error dialog box is displayed when at least one table in the database does not have a valid primary key. This dialog box can appear: on opening, or after conversion to v14 of a database where the Use Log File option is checked, after checking the Use Log File option in a v14 database. 4D v14 Upgrade 25

26 Chapter 2 Development workshop If you have access to the database structure, the dialog box provides several options and displays, when you expand the lower area, the list of tables that do not have a primary key: The following message only appears if the database was using a log file: You then have the following options: Copy: copies information from the window into the clipboard for analysis. Close database: leaves the database intact and closes it. Continue: opens the database without processing the errors. In this case, journaling is disabled for the database (if the Use Log File option was checked, it is unchecked) and the database works perfectly in v14. You can use this option if you do not want to use the log file with your database. Run assistant: displays the Primary key manager window, used to update all the tables of the database. We recommend choosing this option in order to evolve the database. This assistant is described in the following section. 26 4D v14 Upgrade

27 New data journaling If you do not have access to the database structure, it is not possible to enable journaling and 4D will display a message suggesting you contact the database administrator. Primary key manager 4D v14 provides a new assistant, the "Primary key manager", intended to facilitate the resolution of errors related to the presence of tables without primary keys, in the context of a journaled database: You can use this assistant to: diagnose the compatibility of each database table with the 4D v14 journaling mechanism, propose a correction for each table found that is not compatible, more particularly by creating a primary key. Note The Primary key manager is also provided as a v13 component that you can use to prepare 4D v13 databases for conversion to v14. 4D v14 Upgrade 27

28 Chapter 2 Development workshop Displaying the assistant There are two ways to display the Primary key manager window: from the Primary key error window: click on the Run assistant button to display the assistant window: Note The assistant is displayed in Design mode. If the database starts in Application mode, the assistant does not appear right away and you will need to switch to Design mode. from the Structure window: a new button in the tool bar of this window displays the assistant: Access to Primary key manager Using the assistant The Primary key manager window displays a line for every table in the database. Note The assistant does not take tables placed in the Trash into account. The icon at the head of each line indicates whether the table requires the attention of the user: OK A valid primary key is set for the table. No primary key, eligible field(s) No primary key, no eligible fields Warning The table does not have a primary key but contains at least one field that could become the primary key. The table does not have a primary key and does not have any fields that could become one (you will have to create a primary key field). The table does not have a primary key but it is not journaled ("Include in Log File" option disabled for the table). It is possible to hide tables that have this status by unchecking the option to display warnings 28 4D v14 Upgrade

29 New data journaling For each journaled table that does not have a primary key, the assistant displays a menu to set the action to be performed. You can choose from the following options: Ignore: does not modify the table. The errors are not corrected and the status of the table is not changed. Use this option if you wish to intervene later, or if you want to create the primary key outside of the assistant. This option is necessary in particular when you want to create a primary key based on several fields in the table. Use existing field (only shown for tables with at least one field eligible to be a primary key): designates one of the table fields as the primary key. When you choose this option, the assistant suggests the most appropriate field by default. If you want to use another field or if the assistant fails to identify a particularly suitable field (the assistant displays "Select a field"), click on the second menu in the row to display the list of eligible fields. Create a new field: creates a new primary key field in the table. This field will have the same characteristics as the one added by default when a new table is created (see the Default primary key field paragraph on page 23). By default, the assistant proposes to create a field of the Longint type, named "ID". You can modify the name and type of default primary key fields in the Preferences (see the "Primary Key" preferences paragraph on page 24). You can access this page of the Preferences by clicking on the button in the Primary key manager. You can also change the name and/or type of the field directly in the Primary key manager window. Do not log this table: unchecks the "Include in Log File" option for the table. You can choose this option in the case of temporary tables (see the "Include in Log File" Option paragraph on page 22). After you validate this dialog box, a "Warning" status is assigned to the table. 4D v14 Upgrade 29

30 Chapter 2 Development workshop Once you have made your settings, click on Apply... to apply the changes to the database or Close to close the dialog box without modifying the database. When you click on Apply..., a confirmation dialog box appears listing the operations to be performed, then you can either Apply or Cancel the operation: If you have designated existing fields as primary keys, 4D checks each table to make sure that its existing data respects the rules concerning uniqueness and null values for this type of field. If, for example, a field contains duplicate values or null values, an error is generated: You will need to find and remove these anomalies before you are able to enable journaling for the data. Viewing the primary key in the MSC The Activity analysis page of the MSC was modified in order to display the primary key values of the records. The Record/BLOB column is now named Primary Key/BLOB and displays the contents of the primary key for each record. When the primary key consists of several fields, the values are separated by semicolons. The record numbers are listed in a new column on the right of the page. 30 4D v14 Upgrade

31 Debugging help Several new features in 4D v14 aim to facilitate debugging and maintenance of 4D applications. Debugging help Note A new format is also available for the debug log file. For more information, refer to the SET DATABASE PARAMETER, Get database parameter paragraph on page 147. Ignoring errors In the syntax error window, if you hit Alt (Windows) or Option (OS X), the current error is no longer indicated in the session. From then on, in this case, the Continue button changes to Ignore in order to indicate this functioning: Real Time Monitor 4D v14 offers a new function to monitor in real time the progress of "long" operations performed by the application. These operations are, for example, sequential queries, execution of formulas, etc. 4D v14 Upgrade 31

32 Chapter 2 Development workshop This function is found on the new "Real Time Monitor" page of the 4D Server Administration window: This page is available in the administration window of the server machine and also from a remote 4D machine. In the case of a remote machine, this page displays data from operations performed on the server machine. A line is added for each long operation performed on the data. This line automatically disappears when the operation is complete. The following information is provided for each line: Start Time: starting time of operation in the format: "dd/mm/yyyy - hh:mm:ss" Duration (ms): duration in milliseconds of operation in progress Information: title of operation. Sub-operations: dependent operations of the selected operation (lines containing sub-operations are displayed in bold). 32 4D v14 Upgrade

33 4D components The page is active and updated permanently as soon as it is displayed. It should be noted that its operation can significantly slow the execution of the application. It is possible to suspend the updating of this page in one of the following ways: clicking on the Pause button, clicking in the list, pressing the space bar. When you pause the page, a "PAUSED" message appears and the button label changes to Restart. You can resume monitoring of the operations by performing the same action as for pausing. Note Real-time monitoring of operations is also available using a new command, GET ACTIVITY SNAPSHOT, which contains additional options. Starting log files On the "Maintenance" page of the 4D Server Administration window in v14, the button used to start the request log also starts the recording of debug events. It is now labeled Start Request and Debug Logs: Two files are now generated in the database Logs folder when you click on this button: 4DRequestsLog_N 4DDebugLog.txt 4D components In 4D v14, the new On Host Database Event database method facilitates the initialization and backup phases for 4D components (see the On Host Database Event paragraph on page 160). 4D v14 Upgrade 33

34 Chapter 2 Development workshop For security reasons, you must explicitly authorize the execution of this method in each host database. To do this, you must check the new Execute "On Host Database Event" method of the components option on the "Security" page of the Database Settings: By default, this option is not checked. When this option is checked: 4D components are loaded, each On Host Database Event database method of the component (if any) is called by the host database, the code of the method is executed. When it is not checked: 4D components are loaded but they have to manage their initialization and backup phases themselves (as in previous versions of 4D). 34 4D v14 Upgrade