SQLEditor+4.0.rarSQLEditor+4.0.rarSQLEditor+4.0.rarSQLEditor+4.0...

================================= RELEASE NOTES FOR Informix Database SQL Editor 4.0 for Microsoft Windows Platforms DATE: 8/27/99 ================================= TABLE OF CONTENTS I. OVERVIEW OF RELEASE NOTES II. SUPPORTED DATABASE SERVERS III. PRODUCT OVERVIEW IV. ADDITIONAL FEATURES, LIMITS, AND RESTRICTIONS V. KNOWN PROBLEMS +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ I. OVERVIEW OF RELEASE NOTES ============================== These release notes are written for system administrators and database administrators who use the Informix SQL Editor. These release notes describe any special actions required to configure and use the SQL Editor on your Microsoft Windows computer, and contain information about known bugs and their workarounds. This release notes document is not intended to be all-inclusive; use it as an addendum to the on-line help that accompanies each tool. II. SUPPORTED DATABASE SERVERS =============================== The SQL Editor is a stand-alone executable programs that run on Windows computers. To run this tool, your client computer must have Informix Connect installed. The SQL Editor supports the following servers: o Informix Dynamic Server Version 7.3, for UNIX and Windows NT o Informix Dynamic Server Version 8.3, for UNIX o Informix Dynamic Server 2000 Version 9.2, for UNIX and Windows NT III. PRODUCT OVERVIEW ===================== The SQL Editor enables you to execute SQL statements and view results. For information on using this tool, see the on-line help. IV. ADDITIONAL FEATURES, LIMITS, AND RESTRICTIONS ================================================== This section provides information about additional features not described in the on-line help. It also provides information about limits of and restrictions on features that are described in the documentation. A. OS-EQUIVALENT LOCALES -------------------------- If you use the SQL Editor to connect to a database that was created with an OS-equivalent locale, you may receive an "Unable to locate the locale or conversion file" error message and the connection attempt will not be successful. To fix this problem, follow these steps: 1. Find out the locale of the database. You might have to query the sysmaster database table to get this information. 2. Obtain the International Language Supplement (ILS) CD-ROM from Informix. 3. Install the files for your database's OS-equivalent locale and collation locale (for example, C) from the CD-ROM onto your client computer. 4. Use the Client Configuration Environment Properties dialog box (or Setnet32) to change your CLIENT_LOCALE and DB_LOCALE parameters to match the OS-equivalent database locale. 5. Relaunch the SQL Editor. B. LOCALE SETTINGS ARE READ EACH TIME A CONNECTION IS ATTEMPTED ----------------------------------------------------------------- The SQL Editor reads the GLS environment variables every time an action is performed at the server level (for example, CREATE DATABASE) and every time the database locale in the new connection changes. Thus, databases are created according to the most recent value of DB_LOCALE. Likewise, changes to CLIENT_LOCALE might affect the SQL Editor. For all database connections, the effective value of DB_LOCALE is always the actual locale of the database. C. VIEWING IMAGES WITH THE SQL EDITOR CELL VIEWER --------------------------------------------------- The SQL Editor Cell Viewer window does not support image file formats that rely on LZW compression (such as GIF and TIFF LZW). D. USING THE SQL EDITOR ON VERY LARGE TABLES ---------------------------------------------- When you use the SQL Editor to browse very large database tables (20,000 rows or more) or to execute queries that return several columns of very large data types, be aware that it can take several minutes for the SQL Editor to read from the tables and display the output data. V. KNOWN PROBLEMS =================== This section describes the problems known to exist in this release. Bug 081907: FOR UPDATE Clause Not Supported The FOR UPDATE clause is not supported by the SQL Editor. However, if you include a FOR UPDATE clause in an SQL statement submitted by the SQL Editor, you do not receive a syntax error. The statement executes successfully, but the rows selected are not available for update by subsequent SQL statements. Bug 091772: Null Values in a Row Type are Inserted as Zero If you use the SQL Editor to insert a null value into a row type, the value is inserted as 0 (zero). Bug 106871: Cannot LOAD from SQL Editor to Table with ifxdocdesc Column The SQL Editor does not correctly handle a null row type when you write datato a table with an ifxdocdesc column (from a text DataBlade module). The following message is displayed: SQL Editor - error 9634 - "No cast from lvarchar to ifxdocdesc" Bug 109048: Cannot SELECT a Row Containing a Column of Type ifxdocdesc If you use the SELECT statement on a row containing a column of type ifxdocdesc (from the text DataBlade module), the SQL Editor does not correctly handle a null row type, and it crashes. Bug 115177: selecting from table that contains user-created row types displays random characters for row type data, though data is inserted correctly.