5 - Implemented a simple data compression algorithm for use within the Client/Server environment to reduce data transmission requirements.

Transcription

1 - README FILE - ProvideX ODBC Driver Versions 4.10 & 4.00 June 2006 Sage Software Canada Ltd 8920 Woodbine Avenue Suite 400 Markham, Ontario L3R 9W9 Tel *** NOTES *** Version 4.10 is a minor release that contains the latest additions & changes to the ProvideX ODBC driver. It replaces Version 4.00 in its entirety. This document contains all of the release notes for Versions 4.00 and 4.10 of the ProvideX ODBC driver. ProvideX ODBC Driver Version 4.10 June Addressed an issue reporting an incorrect data type to Microsoft SQL Server. The driver now uses the SQL_VARCHAR data type instead of SQL_CHAR for all string types which may not be padded to their full length; e.g., for DELIMITED fields and for FIXED segments of an external key. 2 - Resolved an issue where it was possible to write a record to a file which was larger than the defined record size. Previously, writing a record larger than the record size could damage the file resulting in an Error #108 (Keyed file error (Record length invalid)) when attempting to open the file within ProvideX. 3 - Added ODBC server support for the SunSparc8 and above. 4 - Corrected the implementation of the SQLTables() function to allow either a specific table name or a null table name to select all tables in the datasource. 5 - Implemented a simple data compression algorithm for use within the Client/Server environment to reduce data transmission requirements. 6 - Added optimization of SQL SELECT statements that contain LEFT OUTER JOINed tables and an ORDER BY clause. This optimization can be disabled through the use of an environment variable, PVK_OPTIMIZE_OJ. If PVK_OPTIMIZE_OJ exists and is equal to zero the optimization will be disabled. 7 - Implemented version control to ensure compatibility between components of the ODBC driver. Version checks include: a) Client side - Driver to IO Library b) Server side - Server to IO Library c) Client to Server. Attempting to use mismatched versions will produce an error message. 8 - Added the following error message when the 'security:' tag is missing from the configuration file (pvxiosvr.conf) on UNIX and Linux servers: [ProvideX][ODBC Driver][FILEIO]Security configuration is invalid 1

2 9 - Resolved a problem with incorrect results being returned when using a partial value with a 'GREATER THAN' clause. For example, SELECT ItemNumber FROM InventoryMasterfile WHERE ItemNumber > '1001' Did not return values such as: 1001-HON-H HON-H252LK 1001-HON-H HON-H254LK 10 - Addressed an issue where the driver could incorrectly report an 'Unable to locate record for the requested key' error when the first record of a nonnormalized file was shorter than its defined length Improved support for arrays defined via the ProvideX Data Dictionary Added a 'Strip trailing spaces' option to the DSN setup with a corresponding connection string option of 'StripTrailingSpaces=' with values of 1 (true) or 0 (false). This option provides the ability to compare spacepadded and delimited values. For example: FIELD1 is defined as STRING, LEN=5, DELIMITED and has a value '123' FIELD2 is defined as STRING, LEN=5, FIXED and has a value '123 ' If the 'Strip trailing spaces' option is ENABLED, then 'FIELD1=FIELD2' expression is TRUE, otherwise it is FALSE Enabled the use of keys with descending segments in random navigation Resolved an issue where the driver did not recognize upper case INI file extensions. Now both.ini and.ini are supported Addressed an issue where the connection timeout may not initially be set to 0 (no timeout) resulting in incorrect timeout errors. This value can be changed by external applications using SQL API SQLSetConnectAttr() function call Fixed a compatibility issue with MSSQL Server/DTS. The server was failing when trying to import tables with large fields (in excess of 16K) Addressed erroneous reports of "Data Dictionary not found" with MAS90 version 4 systems when the table/path name exceeded 120 characters in length Fixed an incorrect report of "missing table" caused by underscores, "_", in the name. The SQLTables() function was not stripping the backslash, "\" which is used to escape the underscore. If the underscore is not proceeded by a backslash then the underscore is considered as a wild card match for any character. For example, 'AP1_VendorMaster' was presented as 'AP1\_VendorMaster' which made this table inaccessible Corrected a query timeout issue caused by the incorrect application of the connection timeout to the statement timeout. This resulted in early termination of the execution on large reports (long running SQL statements) Resolved an issue where incorrect processing of numeric segments of the primary key could cause the ODBC server to shutdown Corrected storage of SQL_ATTR_MAX_ROWS. The value being set was saved as a 16-bit number instead of a 32-bit number [Client/Server Version Only] Fixed a problem where data files were left 2

3 open if the client application was abnormally terminated or the network connection was broken UNIX/Linux command line options --version and --debug tested for in lowercase as per help text. Previously only all uppercase was being matched [UNIX/Linux Server Only] Changed creation logic of the file pvxiosvr.pid to allow the umask setting to control access by group and other. Previously the file was created with only read-write permission for the user, no access for group or other Fixed a problem where EFF files larger than 2GB could not be accessed on platforms with LFS enabled [New Red Hat Server] Addressed an issue involving Red Hat Enterprise 4 where the incorrect processing of user licenses could cause a new user connection to fail. This occurred due to a compatibility issue with shared memory operations between RedHat 7.2 and RedHat Enterprise 4. Now there is an ODBC Server port specifically for the RedHat Enterprise family. This port should be used on RedHat Enterprise 3 and 4 systems. Older RedHat systems (7, 8, and 9) can continue using the RedHat 7.2 port Corrected a potential GPF in MS Query that could occur when accessing tables with fields defined with a length of 0. ProvideX ODBC Driver Version 4.00 December 2004 ProvideX ODBC Version 4 is a major release that requires a new activation key. This release includes the following changes and new features: - Significant performance improvements - Support for EFF files - Expanded SQL syntax - Redesigned server model - Consolidated local and client installations NEW ACTIVATION KEY REQUIRED A temporary key from a Version 6 Professional or E-commerce, or an upgrade to an existing ODBC key is required to activate the Version 4 ODBC driver. If the activation key currently installed is not a ProvideX Version 6 key, then the driver or server will run in Demo mode. No activation is required if the ProvideX ODBC driver is used with an activated ProvideX IO Server. If the driver is used as a local (no server) ODBC driver, then an activation key is required. PERFORMANCE IMPROVEMENTS Performance was the development focus for this release. The local driver in Version 4 performs significantly faster than in Version 3 and the client-server driver is now, in most instances, faster than the local driver. Server-side support for numeric restrictions is one example of Version 4 improvements. Previously, the restriction of a query on a numeric field was processed on the client-side. In Version 4 of the ODBC driver, the restriction is sent to the server and only records that match the restriction are returned to the client. This significantly reduces network traffic and results in a performance gain. 3

4 ENHANCED FILE FORMAT (EFF) SUPPORT The ability to read and update EFF-based files is available with Version 4. Platform limitations on file size may apply. See ProvideX V6 documentation for additional information. SQL ENHANCEMENTS The following SQL items are now supported. Refer to the revised ProvideX ODBC manual for complete syntax. TOP keyword syntax: SELECT TOP n selectcols FROM tablelist where groupby having Where: n is a positive integer to limit the rowset size to. SQLSetStmtOption attribute SQL_MAX_ROWS: This statement attribute is similar to the TOP keyword; however, the value is applied to all SQL statements processed on the statement handle to which SQL_MAX_ROWS was applied. A TOP keyword in an SQL statement will override the value of SQL_MAX_ROWS. REDESIGNED SERVER MODEL The name of the driver as it appears in the installed drivers listing of the ODBC Driver manager has been changed from "ProvideX 32-Bit ODBC Driver" and "ProvideX 32-Bit ODBC Client Driver" to "ProvideX ODBC Driver". This will allow both Version 3 drivers and Version 4 drivers to be installed on a system without conflict. A new version check between client and server has been implemented to minimize compatibility issues that occur when upgrading only one side of a client server installation. CONSOLIDATED LOCAL AND CLIENT INSTALLATION The local and client drivers are consolidated into a single DLL. The DLL's and executable have been renamed. The local and client DLL's: pvxodb32.dll and pvkiw32.dll (local driver) pvxodc32.dll and pvkic32.dll (client driver) have been consolidated into: pvxodbc.dll and pvxio.dll (both local and client driver) The server executable and DLL: pvxodbs.exe and pvkis32.dll (Windows) or pvxodbs (UNIX/Linux) have been renamed to: pvxiosvr.exe and pvxio.dll (Windows) or pvxiosvr (UNIX/Linux) ADDITIONAL INFORMATION INSTALLATION NOTES: 4

5 The installation routine will only update System DSN's during an upgrade of an existing driver. If you choose to upgrade an existing driver, file and user DSN's will continue to point to the old and now non-existent pre-v4 driver dll's thus making them unusable. File and user DSN's should be removed prior to upgrading from an existing level 3 driver. The Version 4 IO server cannot be running at the same time as any previous version of ProvideX ODBC server. On Windows, the executable uses the same registry entry, thus shares the port number. On UNIX/Linux the servers use the same shared memory ID, and only one instance is allowed. MAS 90, MAS 200 USERS: Please note that version 4.0 of the ProvideX ODBC driver is not compatible with version 4.0 of MAS 90/200. Use of the version 4.0 ProvideX ODBC driver with a version 4.0 MAS 90/200 is not supported. UNIX/Linux NOTES: The ProvideX IO Server now records the pid (Process ID) of the server in a file (pvxiosvr.pid) to assist in shutting down the server. There is a new command line argument available to shutdown the server: pvxiosvr -s or pvxiosvr --shutdown If the server can locate the pvxiosvr.pid file, then the running server will be shut down properly otherwise an error message will be printed to standard out. The ProvideX IO Server now logs startup and shutdown with syslogd (system log daemon). 5