Warehouse Release 3.00.4910

01/25/2005

The features in the 3.00.4910 release are:

 . The type of ODBC database can be displayed with the SHOW statement. 

For example:

     OPEN MYDB ODBC MSACCESSDB

     SHOW MYDB DRIVER

   shows the following for MS Access:

        SQL_DBMS_NAME = ACCESS

        SQL_DRIVER_NAME = odbcjt32.dll

        Driver conformance level = Level 1

        SQL conformance level = Minimum

. The process id (PID) of the logging Warehouse server is now written to the WHLOG file for each log entry. 

  In the following example the WHLOG file, 5872 is the PID:

        14-Jan-05 13:08:53 5872 Login -

        as user QA3 from user QA3 on NT15 (68.27.246.31)

        14-Jan-05 13:08:53 5872 Connection from 68.27.246.31 closed.

  This additional information is of assistance in identifying specific log sources.

. The program name and version number of the product being validated  is now written to the WHVALLOG  file.

  25-Jan-05 13:57:44 Warehouse 3.00.4910-W Entered demonstration code: 7A1A-2E68-49A1-99B6-665D

  25-Jan-05 13:57:44 Warehouse 3.00.4910-W Set expiration date to 20050205

  25-Jan-05 13:57:50 Warehouse 3.00.4910-W Set return code to 155-838-799

. A SET option has been added to allow the user to change the value displayed when a null value is printed. 

   The syntax is:

    SET PRINTNULL "<null-print-value>"

<null-print-value> is the string displayed when a null is   printed with the PRINT statement.  By default, the value is

  "$NULL".

   For example:

    SET PRINTNULL "(null)"

    DEFINE S1, S2 : ORACLE VARCHAR2(10) ALLOW NULLS

    SETVAR S1 = "Taurus"

    PRINT S1, S2, S1 || S2

    GO

    Taurus     (null)     (null)

. The names of the client and server system names are now displayed when using WH -SERVERINFO <system>. 

  Previously only the IP addresses were displayed.  The partial output now looks like this:

    Server IP Address       : 68.27.246.46 (fox.taurus.com)

    Client IP Address        : 68.27.246.44 (eagle.taurus.com)

. Changes were made to allow the construct: X == $NULL

  In prior releases the == operator could not be used to compare with $NULL.  This has been fixed.

. A problem copying the MS Access databases containing DECIMAL columns has been fixed. 

  The cause of this problem appears to be a MS Access ODBC driver bug.  Passing data to MS Access labeled as  "decimal" gave the error:

    Optional feature not implemented (ODBC S1C00)

  A change was made to label decimal data as "char" when writing to a MS Access database.  MS Access accepts this and that appears to have fixed the problem.  Warehouse now checks ODBC connections to see if the connection is to a MS Access database and labels decimal data as char data if it is. 

. Three problems with calling user functions in a FOR condition  have been fixed. 

 A problem introduced in release 3.00.4020 could cause this statement to give an error:

    READ T=DB.TABLE FOR C = USERFUNC(EXP)

  If DB was a REMOTE database and EXP was not a column in TABLE and USERFUNC accessed global variables for FORMAT definitions,  an error would be issued.  In releases prior to 3.00.4020, the  READ statement would work without error.  This has been fixed in this release.

  A problem was also fixed that caused an error when USERFUNC contained a blank line and DB was a REMOTE database.

  Also, the above READ statement would return incorrect records when the comparison involved a null value.  This has been fixed.

Release 3.00.4910 is available now on all supported platforms.