.
contact contact

Eloquence B.07.10 Release Notes (B090130)

 
.
 

Overview

After the release of Eloquence B.07.10 a number of bug fixes and enhancements were released as patches, providing improved functionality, performance and reliability.

The user visible changes implemented through these patches (along with critical bug fixes) are covered in this document (relative to the original B.07.10 release). This includes new features and enhancements that were originally developed for the B.08.00 version, but were also ported back to B.07.10 with patches.

This document extends on the Eloquence B.07.10 release notes and reflects the changes in the Eloquence patch bundle PE71-B090130.

Contents



Database server

Major database server changes include
  • The database server was enhanced to support replication.

  • The database server was enhanced to support case insensitive indexes.

Other database server changes include

  • A compatibility issue with the Linux glibc2.4 (and newer) was corrected.
  • The database property DBLOCK-COMPAT was added to enable mandatory DBLOCKs. While we would usually recommend against using this, it may be required for close TurboIMAGE compatibility in rare cases.
  • Forward log is no longer disabled after a database server crash.
  • The Database server config file template was updated
Please refer to the following documents for details:


Database Client Libraries

Changes to the database client library include
  • A few issues and side effects related to client side caching were fixed.

Changes to the image3k library include:
  • Information passed to the DBBEGIN, DBEND and DBMEMO calls may optionally be included in forward logs.

  • The HP3K_TPI_COMPAT database property supports additional options to improve Superdex compatibility.

  • The TurboIMAGE compatibility was changed to improve corner case compatibility of the DBFIND call. As documented by the TurboIMAGE documentation it now resets the current record number.

  • The username and password passed in the DBLOGIN call may now be up to 255 characters.
Please refer to the following documents for details:


Database Utilities

Database utility changes include
  • The dbrecover utility was enhanced to support point-in-time recovery. The -T command line option may be used to specify a point-in-time to stop recovering transactions from the forward log.

  • The dbrecover utility was enhanced to support incremental recovery. Instead of starting from the last backup, dbrecover has gained the ability to continue where it previously left off.

  • The schema, dbutil and prschema utilities were enhanced to support additional syntax for case insensitive indexes.

  • The new dbrepl utility is used to replicate database transactions to one or more slave servers.

  • The fwaudit utility was enhanced to support more complex filter expressions, to support the "id" and "conntime" filter criteria and to support information from DBBEGIN/DBEND/DBMEMO calls.

Changes to database utilities include

  • The dbrecover, dblogreset, dbstore, dbbexp, dbcfix support custom cache sizes instead of using the server configuration file.
  • The dblogreset utility was enhanced to retain changes in transaction journal, reapplied during startup recovery, in the forward-log after abnormal server termination.
  • The query3k utility defaults to /var/tmp for temporary files.
  • The query3k utility no longer displays max capacity in form set, if default.
  • The query3k utility was enhanced to improve support for Eloquence database limits that exceed TurboIMAGE limits.
Please refer to the following documents for details:


Database logging, auditing, replication, fwutil

Noticeable changes to the forward logging and auditing subsystem include
  • Forward logs and audit files may now include information on the IMAGE3K DBBEGIN, DBEND and DBMEMO calls.

  • The database server and the dbrepl utility support database server replication from archived transactions in the forward log files

  • The new fwutil library provides incremental and close-to-realtime access to database changes and transactions.
Please refer to the following documents for details:


Database performance metrics (server, sessions)

Changes include
  • The server performance metrics were improved; configuration options for StatFileFlags, SessionStatFile, SessionStatMode were introduced and associated dbctl options for dynamic control were added.

Please refer to the following documents for details:


Eloquence Language

Changes to the Eloquence programming language include
  • The SORTORDER config option may be used to specify the collating sequence that is used for sorting (SORT BY statement and LEX function).

  • The QFIND IN statement was enhanced to support case-insensitive indexes.

  • Support for JDLG (pass through) printing was added (using PRINTER IS 10)
Please refer to the following documents for details:


Eloquence WEBDLG

WEBDLG enables dialog based Eloquence programs to use a web browser as a user interface (requires Apache web server).

Changes to the Eloquence WEBDLG include

  • The Eloquence WEBDLG and accompanying APACHE modules were ported to the Windows platform. The APACHE 2.0 and APACHE 2.2 web servers are supported.

  • The Eloquence WEBDLG and related APACHE 2.0 and APACHE 2.2 modules were ported to the 64 bit Linux x86_64 platform.

  • The APACHE web server 2.2 is now supported through the WEBDLG eloq_mod22 module.

  • The mod_eloq2 and mod_eloq22 WEBDLG modules for the APACHE 2.x web server are now compatible with the threaded APACHE 2.x multi-processing model (APACHE 2.x MPM worker). Previous versions of the mod_eloq2 module could only be used with the non-threaded APACHE 2.x multi-processing model (APACHE 2.x MPM prefork).
Please refer to the following documents for details:
  • Eloquence 7.10 documentation for WEBDLG


Eloquence Odbc.DLL

  • Added the SetTextColumnSize procedure to specify the default and maximum size for text columns.

      CALL DLL Odbc("SetTextColumnSize",DefaultSize,MaxSize)

    DefaultSize specifies the size the Odbc.DLL should use for text columns when the ODBC driver does not specify a column size. MaxSize specifies the maximum size for text columns the Odbc.DLL should use. Both must be between 1 and 32767. DefaultSize must not be greater than MaxSize.

    By default, both DefaultSize and MaxSize are set to 1024.

  • The Prepare or ExecDirect procedures could return ERROR 2 due to a memory allocation failure if the ODBC driver specified a huge size for a text column.

    For example, the SQL Server ODBC driver may return a column size of 2.147.483.647 bytes for a LONGVARCHAR column, which is the theoretical LONGVARCHAR column size limit. The Odbc.DLL then tries to allocate a buffer big enough to hold this column size, causing a memory allocation failure.

    The size of the allocated buffer is now limited to the maximum size for a text column, which is 1024 by default but may be configured with the SetTextColumnSize procedure.

  • The GetError procedure now traverses up the error stack in the ODBC driver manager and the ODBC driver. Previously, only the error information from the current context was retrieved.

    For example, in a connection context the connection related error information and in a statement context the statement related error information was retrieved. This way, in rare cases an error message could be missed, for example if the ODBC driver generates a connection related error message in a statement context.

  • A compatibility problem of the Eloquence Odbc.DLL and the FreeTDS ODBC driver was resolved.

    The FreeTDS ODBC does not support the SQLDescribeParam() ODBC function. In this case the data type of an SQL query parameter is unknown. The Odbc.DLL now handles this by binding the parameter at a later stage when the application defines the data type.

    As a consequence, the application should take care to provide an appropriate parameter data type if the FreeTDS ODBC driver is used, otherwise a data type mismatch error may result.


Eloquence IDE (Windows)

Changes to the Eloquence IDE on Windows include

Editor:

  • The program-, text- and dialog-editor windows now display the full path of the edited program/text/dialog file.
  • On saving a program, if a program's size exceeds 64 kilobytes and its file format is either "Compatible Program File" or "A.05.01 Program File", the program file format is automatically changed to "A.06.00 Program File".
Explorer:

  • If a directory is opened, the explorer no longer displays "access denied" on subdirectories. Instead, it is now visually indicated when a subdirectory cannot be accessed.
  • After saving a file the explorer is now refreshed to either add a new file to the file list or update the saved file's properties such as the new file size.
Application Properties / Debug Session Setup:

  • In the Debug Session Setup dialog, a command line may now contain dynamic parameters ($ tokens). Previously, dynamic parameters were only evaluated in the environment string.

    Dynamic parameters allow to dynamically embed the local host name and IP address, the login name and arbitrary environment values. Please refer to the document below for details about dynamic parameters:

    http://eloquence.marxmeier.com/support/A06/relnotes/A0631/ide.html

  • The $I dynamic parameter to embed the local IP address could choose the address of a wrong network adapter if multiple network adapters are configured.
Dialog Editor:

  • After changing a value in the property editor it is no longer required to confirm with the RETURN/ENTER key.
  • An EditText width value of 1 was not always saved to the DLG file.
  • The Dialog x/y position is no longer saved to the DLG file if it is zero.
  • The DLG plugin configuration (ide-adlg.cfg) was updated to cover the recent JDLG object attribute changes.
Miscellaneous:

  • On recent Windows versions the Eloquence IDE issued a "Failed to update the system registry" error message on startup.


eqstart utility (Windows)

Changes to the Eloquence eqstart utility on Windows include
  • In the Eloquence Start File configuration, a command line may now contain dynamic parameters ($ tokens). Previously, dynamic parameters were only evaluated in the environment string.

    Dynamic parameters allow to dynamically embed the local host name and IP address, the login name and arbitrary environment values. Please refer to the document below for details about dynamic para- meters:

    http://eloquence.marxmeier.com/support/A06/relnotes/A0631/ide.html

  • The $I dynamic parameter to embed the local IP address could choose the address of a wrong network adapter if multiple network adapters are configured.

  • The eqstart utility now uses the system-defined temporary directory instead of C:\ on Windows.

 
 
 
  Privacy | GDPR / DSGVO | Webmaster | Terms of use | Impressum Revision: 2009-02-02  
  Copyright © 1995-2024 Marxmeier Software AG