dbExpress driver for SAP DB | To Do

dbExpress driver for SAP DB v. 1.0.2
==========================================

Release date: 03.10.2004

BUGS FIXED IN THIS RELEASE:
===========================

1. Bug in SMALLINT data type support (wrong size from the Borland's point 
of view) is fixed.

2. Bug in DATE and TIMESTAMP data types support (incorrect dates calculation) 
is fixed.

3. SQL query used to get columns metadata has been changed. Now columns are
sorted by position, not by name as in the previous releases.

IMPROVEMENTS AND NEW FEATURES:
==============================

1. Large BLOBs fetch performance was slightly improved (now they are all 
fetched using 32K chunks, the largest possible chunk size supported by 
SQLDBC).

2. Some tests of multithreading was performed. Yes, this driver can be used 
in the multithreaded applications.

KNOWN BUGS
==========

#00002. Driver still does not support adding NULL blobs (values of LONG and 
        LONG BYTE columns) through parameters. We see no way to do it with
        the version of SQLDBC used.

#00005. Driver sometimes incorrectly reports that BLOB (LONG and LONG BYTE)
        columns has NULL values, while their values are not NULL. This
        behaviour is observed only when there are several BLOB columns in
        the table, and depends on the column order.

TODO
====

1.  Support for the rest of SQLDBC connection options.
2.  Carefully check and describe transaction support.
3.  Add support for bulk operations (array binding).
4.  Support setting/retrieving cursor name
5.  Check different SQL Modes (besides default, Internal)
6.  Full support for FIXED columns without precision limitations 
    (depends on libSQLDBC.dll version)
7.  Test OUT parameters in DBPROC: SQLCommand::getParameter method
8.  Implement real check that columns are Writable (depends on 
    libSQLDBC.dll version). Now they are all writable (but DEFAULT SERIAL 
    should not be).
9.  Write project documentation (at least, as comments in headers).
10. Make more benchmarks and performance tests
11. Check whether driver works with MaxDB (it should work, but more 
    tests needed).
12. Add workaround for the primary key columns, for which no
    separate indexes reported.

PROBLEMS
========

1. Dual licensing scheme for MaxDB should be checked.
2. Transition to newer version of SQLDBC is desired, to get 
   rid of some strange bugs/"features" 
3. More help from the OpenSource and SAP DB developers community is needed.