 - added
 - fixed
 - changed
|
|
| Jun 07, 2006 build 1.2.4 |
|
|
|
|
|
|
if DB_LOCALE and CLIENT_LOCALE were different TEXT parameter value converted with errors |
|
|
|
from this build data fetch from cursor updates SQLCA value accessible with IInformixConnection interface |
|
|
| Jan 20, 2006 build 1.2.3 |
|
|
|
|
added support into installation for Delphi 2006 |
|
|
|
|
|
|
| Jun 22, 2005 build 1.2.2 |
|
|
|
|
|
|
in seldom cases NULL was written instead of TEXT or BYTE value |
|
conversion fix for the floating decimal type when fraction of the value is more then 16 |
|
|
|
|
| Apr 06, 2005 build 1.2.1 |
|
|
|
|
|
|
WaitOnLocks=False actually set WaitOnLocks=True |
|
for SQLDataSet.SetSchemaInfo(stColumns, ...) resultset returned with empty COLUMN_TYPENAME field for simple datatypes |
|
|
|
|
| Feb 22, 2005 build 1.1.8 |
|
|
|
|
|
|
empty string stored as NULL instead of '' value |
|
|
|
|
| Feb 22, 2005 build 1.2.0 |
|
|
|
|
|
|
the "Connection name in use" issue when THREAD MODE is set to INTERTHREADED (FETCH OPTIMIZED). Also fetch performance for this mode is improved |
|
|
|
Informix Connect requirement has been changed from the 2.80 version to 2.30 |
|
|
| Feb 02, 2005 build 1.1.7 |
|
|
|
|
|
|
issue with convertion of DATETIME YEAR TO MONTH and MONTH TO MONTH values when month is February |
|
|
|
updated beginTransaction method to be more compatible with databases running in ANSI mode |
|
|
| Oct 01, 2004 build 1.1.5 |
|
|
|
|
manual has been added to the installation |
|
THREAD MODE connection string paramater |
|
|
|
money field conversion error for values >= 0 and < 1 (when value is 0 "Unknown exception caught" message occasionally occurred) |
|
|
|
|
| Sep 01, 2004 build 1.1.2 |
|
|
|
|
|
|
|
|
Client_Locale=en_us.8859-1 value is removed from default connection string. Because in some cases when DB_LOCALE differs from CLIENT_LOCALE Informix client crashs down during connection |
|
|
| Aug 17, 2004 build 1.1.1 |
|
|
|
|
|
|
connect issue "Cannot set isolation level" with databases that doesn't support transactions (have no logging) |
|
|
|
database changing logic. "close database" or "create database" statement execution clears handles for SQL statements and cursors as well as "database" statement |
|
|
| Aug 09, 2004 build 1.1.0 |
|
|
|
|
IInformixConnection.IsDynamicServer function. Returns True if connected to Dynamic server family |
|
IInformixConnection.IsUniversalServer function. Return values: 1 - connected to 9.xx server family, 0 - connected to pre-9.xx server family, -1 - error occured (check ErrorMessage property) |
|
IInformixConnection.SessionID function. Returns connection's session ID on a database server (same as onstat command displays), if -1 is returned check ErrorMessage property |
|
each error occured at the driver level can be logged by TSQLMonitor component |
|
|
|
issue with "database" statement. If there are opened cursors before executing "database" statement, these cursors will be closed by a database server after execution of "database" statement. Working with such cursors can lead to serious errors and even to a database server crash. From this build after "database" statement execution driver clears handles for such invalid cursors |
|
disconnect issue with Informix Online 5.0 server |
|
|
|
WaitOnLocks parameter when specified in connection string (HostName parameter) could have numeric value (not only True and False). This value specifies number of seconds to wait |
|
ServerVersion returns nil if there was an error while detecting Informix server version. Check ErrorMessage property for description |
|
IsolationLevel parameter removed from connection string to prevent issues with isolation level which will be set by Data Snap throught PSStartTransaction method. To specify isolation level in TSQLConnection parameters use "InformixLuxena TransIsolation" parameter |
|
CommitRetain default value changed to True |
|
|
| Jul 19, 2004 build 1.0.9 |
|
|
|
|
support of eConnServerVersion option |
|
IInformixConnection.ServerVersion method |
|
refresh of server and database features after "database" statement is executed |
|
|
|
DB_LOCALE parameter issue which raised an exception when parameter was specified in a connection string |
|
|
|
|
| Jul 13, 2004 build 1.0.8 |
|
|
|
|
IInformixConnection interface has been ported to Delphi 8 |
|
demo project files for C++ Builder |
|
|
|
installation issue with ini files |
|
|
|
demos have been updated for Delphi 8 compatibility |
|
method IInformixConnection.getLastInsertedSerial8 now returns TBcd or Double value depending from mapping for int8 type |
|
trial build has been compiled with multi-threaded runtime library instead of single-threaded |
|
|
| Jun 28, 2004 build 1.0.7 |
|
|
|
|
|
|
possible access violation on connect has been fixed (affects Windows versions) |
|
|
|
workaround concerns Borland's "database" connection parameter length restriction, which couldn't be more then 255 characters. When parameter value exceeds this limit memory corruption occurs in TCustomSQLDataSet.SetSchemaOption method. From now "database" parameter intend only for database name definition. To specify other connection string parameters use HostName connection parameter. For example:SQLConnection.Params['HostName'] :=
'InformixServer=ol_server; lvarchar=blob';
SQLConnection.Params['Database'] := 'stores_demo'; |
|
|
| May 20, 2004 build 1.0.6 |
|
|
|
|
Kylix version of dbExpress driver for Informix Pro |
|
|
|
|
|
|
| May 15, 2004 build 1.0.5 |
|
|
|
|
|
|
|
|
small fixes in metadata interface implementation |
|
|
| Apr 29, 2004 build 1.0.4 |
|
|
|
|
mapping for decimal, money, int8 and serial8 Informix types to ftFloat, ftCurrency, ftBcd or ftFmtBcd Delphi types. Use connection string to specify which mapping to use, for example: decimal=Bcd - (available values are Float, Currency, Bcd or FmtBcd). By default decimal is mapped to ftBcd (changed from ftFmtBcd), money to ftCurrency, int8 and serial8 to ftFmtBcd |
|
|
|
issue with ftFmtMemo parameters. In some cases last char lost |
|
|
|
|
| Apr 27, 2004 build 1.0.3 |
|
|
|
|
|
|
Trim Char and WaitOnLocks connection string parameter issue. Only uppercase values were recognized (TRUE or FALSE) now parameters is case insensitive |
|
|
|
default installation folder changed to %Program Files%\Luxena\dbExpress Informix |
|
|
| Apr 14, 2004 build 1.0.2 |
|
|
|
|
|
|
access violation issue when lvarchar column contains empty string value |
|
|
|
|
| Apr 01, 2004 build 1.0.1 |
|
|
|
|
getLastInsertedSerial8 procedure in IInformixConnection interface |
|
demo on superstores_demo database |
|
|
|
last inserted serial access issue. Occurred after any component that was bounded to the TSQLConnection was freed, connection area (where serial was contained) were changed |
|
index column position number in indices cursor issue (numbering started from 2 instead of 1) |
|
syntax error in interrupt SQL demo on Informix 7 servers |
|
|
|
|
| Mar 31, 2004 build 1.0.0 |
|
|
|
|
query execution break |
|
mapping for lvarchar type to ftFmtMemo or ftString. Use connection string to specify which mapping to use (LVARCHAR=BLOB or LVARCHAR=STRING). By default lvarchar now is mapped to ftString |
|
|
|
|
|
|
| Mar 18, 2004 build 1.0.0 Beta 3 |
|
|
|
|
connection string feature |
|
|
|
|
|