Pervasive.SQL Connectivity Kit Version 5.0 (Build 39)

Transcription

1 Pervasive.SQL Connectivity Kit Version 5.0 (Build 39) Contents 1. General 2. Registration 3. Obtaining Updates 4. Obtaining Database Builder 5. Supported Environments 6. Release Notes for Version DFBTRDRV.INT sample file with 'best performance' settings. 8. Changes since build IMPORTANT!!! If you are upgrading from an earlier version of the Pervasive.SQL Connectivity Kit, read the Release Notes for Version 3.0 section carefully before upgrading!! 1.General This readme file contains information that does not fit into the Connectivity Kit help or was not known at the time it was created. Please read this information carefully. Please, report any problems you find in the Data Connectivity newsgroup at: news://news.dataaccess.com/data-connectivity 2. Registration During the installation process you will be asked to register the product. This registration can only be done when you have a valid registration code for the 5.0 revision of the Connectivity Kit from Data Access. If you don't have this code, the installation program will automatically register an evaluation license, which allows you to use the driver for a period of 60 days. After that period you will need a valid registration code to continue to use the product. The Connectivity Kit will not run without a valid registration code even if you reinstall it. 3. Obtaining Updates Data Access Worldwide may upload newer versions of the Pervasive.SQL Connectivity Kit to the Data Access Worldwide ftp site. If this happens, it will be announced in the Data Connectivity Newsgroup. If an update is uploaded it will be placed in: ftp://ftp.dataaccess.com/pub/products/connectivity/pervasive/software/ 4. Obtaining Database Builder This version of the Connectivity Kit requires Database Builder (or higher). If you do not have a Visual DataFlex 11.1 license (or higher), the DatabaseBuilder installation will install all the appropriate files and registry settings to use Database Builder DatabaseBuilder exe is placed in the main Connectivity folder during installation and there is a shortcut on the Start menu to start that installation program. 5. Supported Environments DataFlex: Visual DataFlex 8 or higher. DataFlex Console Mode 3.2 Pervasive SQL: Pervasive.SQL V8 (including 8.5 and 8.6) and V9 6. Release Notes for Version Support for Pervasive.SQL V8.5 secured databases. Refer to the Database Mode and Security section of the User s Guide. 6.2 Path information in FILE.DDF Earlier versions of the Connectivity Kit would sometimes generate full pathnames in the XF$LOC field in FILE.DDF. Specifically this would happen when converting to Pervasive.SQL and having a full path specified in the BTR_PATH setting in DFBTRDRV.INT. The Connectivity Kit 3.0 will no longer store full paths in the DDFs. 6.3 Changed error text in dferr005.dat

2 The text of the error codes referring to Pervasive.SQL status codes has been changed in dferr005.dat. BTRIEVE: has been replaced with PSQLerr xx, where xx is the Pervasive.SQL status code. 6.4 Changed Defaults The default values of the following DFBTRDRV.INT settings are changed: USE_CACHE default is now TRUE REPORT_CACHE_ERRORS default is now TRUE 6.5 Slower restructures in database mode with Pervasive.SQL 8.5 and 8.6. Due to a bug in Pervasive.SQL version 8.5 and 8.6 the restructure logic will copy all records two times during restructure of a PSQL table. This will only happen when running in Database_Mode _and_ running on Pervasive.SQL 8.5 or 8.6. The bug has been fixed by Pervasive and will be available in the next revision of Pervasive.SQL after 8.6. There is also a patch (FTF) available that will solve the issue for Pervasive.SQL 8.6. If the FTF fix is installed, the version of Pvsw\Bin\Ntmkde.dll (Windows) or nwmkde.nlm (Netware) must be or later. The Connectivity Kit will detect if the FTF is installed and will use the normal logic (copy once) during restructure. 7. DFBTRDRV.INT sample file with 'best performance' settings. The Connectivity Kit includes two sample configuration files. These files (DFBTRDRV_DEFAULTS.INT and DFBTRDRV_PERFORMANCE.INT) are installed in the \bin folder, where the Connectivity Kit has been installed. DFBTRDRV_DEFAULTS.INT contains all possible configuration settings, with their default values. Additional information is available in the User s Guide. DFBTRDRV_PERFORMANCE.INT contains the configuration settings that will give the best performance with typical (Visual) DataFlex applications. Tests have shown that using these settings can improve performance significantly. The Connectivity Kit installation automatically sets DFBTRDRV.INT to the higher performance settings, unless there is an existing DFBTRDRV.INT file (this will be left as is). Read the information in the User's Guide about these settings. Depending on the type of application you are using, some settings may have side effects. 8. Changes since build BUILD: Implemented the new connectivity enabled registration codes and also changed revision to match the revision of the rest of the connectivity kits. BUILD: Uses CKDaemon instead of DFDaemon. BUILD: If one of the following changes was made as the only change during a restructure, the DDFs and/or INT files would not be updated: Renaming a column (field) Changing the field index Adding/Removing relations BUILD: On some older Pervasive.SQL versions, during open or login, a dfbtrfileextendedstatsub4 error was generated. NATURE: STATUS : Bug Fixed

3 BUILD: Improved structure_end rollback logic. If an error occurred during the restructure of a table, the Connectivity Kit did not always rollback the changes already made. This could lead to additional errors and even an inconsistent table on the next restructure attempt. BUILD: The Connectivity Kit was unable to return a numeric or date field as a string. This would be the case when a Pervasive.SQL numeric/date field is defined with FIELD_TYPE ASCII in the INT file, or when an API function requests to return a numeric/date field as a string. NATURE: Incompatibility BUILD: Added support for setting the DF_FIELD_OLD_NUMBER attribute. This attribute can be used to move data from one field to another during a restructure. Refer to the VDF help for further information on this attribute. BUILD: Fixed a bug with Find GE and Find LE on non-unique indexes. On a table with no recnum support, indexes that have recnum as the last segment are non-unique indexes. These indexes are created as duplicatable keys on Pervasive.SQL. In the following code Find Eq By Recnum Find Ge By Index.1 // (NonUnique Index) If the first Find would find a record in the middle of a series of duplicates, the second Find would find the first record of the duplicates. (Instead of the same record as the first Find) BUILD: After changing the order of the index segments in an index in some circumstances a PSQL status 45 (The specified key flags are invalid) was generated. BUILD: When changing the definition of a numeric field without changing the length (for example from 5.0 to 3.2), the data was not converted properly. (Value 1 would become 0.01) BUILD: Fill_Field of the recnum field on a table without RecnumSupport caused an incorrect overwrite of the first 4 bytes of the buffer. BUILD: Opening tables in multiple databases would occasionally generate status 3006 errors on close or logout. Status 37 errors could be generated on lock or start_transaction., when logged in to multiple databases. BUILD: In a True nullable table, containing a nullable column of type TIMESTAMP (Btriieve type 20): Move zero to Table.TimeStampField or clearing the buffer will set the field to NULL.

4 BUILD: An error message containing an URI would sometimes not hide the password. BUILD: Including Dfbtrdrv.Pkg in a console mode program where no Error.Pkg was used would give compiler errors. BUILD: Extra check added: When using Uri Open As and no URI_OPEN_AS_CACHE_PATH is specified an error No URI_OPEN_AS_CACHE_PATH specified. will be raised. BUILD: Added support for URI dependent cache files when using Open As with an URI. New configuration keyword added for Dfbtrdrv.Int : URI_OPEN_AS_CACHE_PATH If specified this keyword must contain a valid folder name. Example: URI_OPEN_AS_CACHE_PATH C:\Project\Order11PSQL\Cache The URI_OPEN_AS_CACHE_PATH will only be used when running in Database_Mode and an Open As with an URI is performed. The hostname and database name from the URI will be added as subfolders to the URI_OPEN_AS_CACHE_PATH to create a folder name where the cache files will be expected or created. Example: When having: URI_OPEN_AS_CACHE_PATH C:\Project\Order11PSQL\Cache The following Open As Open "dfbtrdrv:btrv://mm@mypsqlserver/order?table=salesp" As Salesp will expect the cache file in: C:\Project\Order11PSQL\Cache\mypsqlserver\order\salesp.CCH The folder specified in URI_OPEN_AS_CACHE_PATH must exist and will not be created by the Connectivity Kit. The hostname and database name subfolders will be created if they do not exist and the Connectivity Kit is writing a cache file. BUILD: Relates on numeric 15.0 fields would fail in some circumstances. BUILD: The Fill_Field command would fill floating point type fields (type 2 (REAL and DOUBLE) and type 9 (BFLOAT)) with incorrect high or low values. BUILD: The connectivity kit was unable to access secured databases in Pervasive.SQL 9. This is now fixed. BUILD:

5 After adding a true nullable date field to an index, a status (Index segment field structure mismatch) was generated on open. BUILD: During a restructure, the Field_Map command returned an incorrect field number for a new added field. BUILD: Status 20568: Invalid Nullable Column was generated after changing the table structure with a SQL statement. The check that triggered the error was incorrect. Fixed. BUILD: Creating a new table with the Visual DataFlex 11 Database Builder would generate a status 22 error. (c) Copyright 2007, Data Access Worldwide All Rights Reserved Worldwide