RELEASE NOTES FOR
IBM Informix ESQL/C Programmer's Manual
Version: 9.51
I. Overview
II. New Features
a. Syntax changes in SQL to support 8.31 product
III.
Fixed
Problems
I. Overview
The purpose of these release notes is to make
you aware of any special actions required to configure and use Informix ESQL/C
on your computer. This file also describes new features and feature differences
from earlier versions of this product and other Informix products, and how
these differences affect current products. In addition, this file contains
information about known bugs and their workarounds.
This release notes document is not intended to be all-inclusive; it should be used as an addendum to the Informix ESQL/C Programmer's Manual, which provides thorough information about product features and behavior.
These release notes are written for the following audience:
System administrators who install Informix
database servers
Database administrators who control access to
Informix databases
Developers who write applications using
Informix ESQL/C
Version 9.40 of Informix ESQL/C has been tested with the following database server configurations:
Informix Dynamic Server, Version 5.10
Informix Dynamic Server, Versions 7.24 and 7.3x
Informix Dynamic Server with Advanced Decision
Support and Extended Parallel Options, Version 8.21 and Extended Parallel
Server, Version 8.3x
Informix Dynamic Server with Universal Data
Option, Version 9.2x (Windows NT) and Informix Dynamic Server 2000, Version
9.2x (UNIX)
Informix SE 7.24
Informix ESQL/C includes source code files for many of the examples in the Informix ESQL/C Programmer's Manual. The installation process copies these source code files into the following directory: $INFORMIXDIR/demo/esql
For more information about the example files for Informix ESQL/C, see the Introduction to the Informix ESQL/C Programmer's Manual.
II. New Features
A. Syntax changes in SQL to support
8.31 product
Refer to ESQL/C doc notes for more details.
Feature 12. Duplicate table to address the XPS server.
III. Fixed Problems
Following problems have been fixed since the
9.5 release.
Bug Number |
Description |
133682 |
IN ESQL VERSION 9.30.UC1 THAT COMES WITH SDK 2.40, IF YOU DO NOT LEAVE ASPACE AFTER A LINE BEFORE A COMMENT, IT GIVE A SYNTAX ERROR |
135070 |
USING AN ARRAY THAT IS MORE THAN 10 ENTRIES CAUSES ESQL COMPILE TO REPORT A -201 ERROR |
135792 |
ENGINE CRASH CAUSE BY CLIENT SENDING PUTINSERT SQLI MESSAGE FOR A STATEMENT WHICH HAS BEEN FREED OR REUSED |
144171 |
PROTOTYPE (DECLARATION) FOR LIBRARY FUNCTION SQLDONE() NOT IN PROVIDED HEADERFILES |
144326 |
RSETNULL(SQLDATE,PTR) USES AN 8BYTE VALUE FOR INTNULL BUT DATE DATA TYPE IS ONLY 4 BYTES WHICH RESULTS IN BUS ERROR ON 64 BIT PLATFORMS |
149277 |
PREPROCESSING ESQL/C, SYNTAX ERROR WHEN SEMICOLONS REMOVED FROM PARAMETERS AFTER USING LITERAL INTERVAL IN PRIOR FUNCTION |
149743 |
COMPILING THE ESQL DEMO3 APPLICATION USING -THREAD OPTION CAUSES MEMORY LEAK |
150359 |
EVENTHOUGH LENGTH OF THE CURSOR NAME IS < 18 CHAR, GETTING ERROR -200 WHILE OPENING THE CURSOR WHEN THE PROGRAM IS COMPILED WITH "-LOCAL" OPTION |
151374 |
MEMORY LEAK CAUSING -406 ON XA CLIENT (TUXEDO SERVICE)
RUNNING TX IN A LOOP |
151375 |
ERROR -258 IN XA ENVIRONMENT AFTER WE EXECUTE A STATEMENT IN A TMJOIN'ED TX. CLIENT WILL SEND -1 SQLID TO THE SERVER |
153225 |
CORE DUMP WHEN ACCESSING LVARCHAR IN DESCRIPTOR AFTER IFX_VAR_DEALLOC |
155189 |
ON HP GETLOGIN_R RETURNS 0 ON SUCCESS AND ERROR ON FAILURE. THIS IS INCORRECT IN OSFUTIL.C |
156116 |
IF PREPARE HAS RETURNED AN ERROR, DOING AN EXECUTE OF THIS STATEMENT GIVES A CORE DUMP IN XA ENV |
133201 |
FRONTEND SHARED MEMORY CONNECTIONS MAY HANG DUE TO A RACE CONDITION ON THE CONNECTION SEMAPHORE |
154103 |
SHARED MEMORY DATABASE CONNECTIONS ARE NOT BEING RELEASED BY ESQL 'DISCONNECT CURRENT' COMMAND AND REMAIN UNTIL EXECUTABLE FINISHES |
155895 |
XA CLIENT LEAKS MEMORY, IN CASE YOU DO A PREPARE, EXECUTE, FREE IN A LOOP AND A NEW TRASACTION IS DONE EVERYTIME |
155447 |
SQL 604 ERROR USING ESQL/C "ARRAY FETCH" WHEN DEFINING ARRAY SIZE TO BE 1 OR 2. THIS ALSO CAUSES CLIENT TO HANG INDEFINITELY |
Copyright © 2002, IBM
Corporation All rights reserved