*********************************************************
*            MyODBC 3.51 Release Notes	      	        *
*             Version 03.51.05 (Gamma)                  *
*              Updated : 18 Dec 2002   	                *
*	 (C) Copyright MySQL AB 1995-2002               *
*********************************************************
        
================================================
CONTENTS
================================================
1. NEW FEATURES IN THIS RELEASE
2. BUG FIXES IN THIS RELEASE
3. OPEN ISSUES
4. TODO LIST
5. NOTES

================================================
1. NEW FEATURES IN THIS RELEASE
================================================
This is the gamma release of MyODBC 3.51.05. This 
should be the final release in the development series 
before making the stable announcement unless if 
there is any criticil bugs from this version. 

So, please test this, and let us know the status back 
to proceed onto stable release.
   
================================================
2. BUG FIXES IN THIS RELEASE
================================================

-- Fix for the thread-safe library core dumps when the 
   driver is built with the debug options. 

-- Fix for OpenOffice to return valid list of catalog 
   names SQLTables along with a valid catalog name.

-- Fixed SQLTablePrivileges and SQLColumnPrivileges to 
   return each privilege type in a individual rows.

-- Fixed the time connersion format error from SQL_TIME_STRUCT

   (Thanks to Ocke Janssen<ocke.janssen@sun.com> for the 
    above 3 bugs from OpenOffice team).

-- Fixed SQLSpecialColumns coredump on HP-UX (threaded 
   library)

-- Fixed SQLGetTypeInfo to return individual rows for 
   auto_increment status for all numeric types.

   (Request from Gerry Sweeney <gerry@support-works.com>)

-- Fixed to return an error when the conversion is from 
   SQL_C_NUMERIC as the driver is not cabale to handle 
   SQL_NUMERIC_STRUCT conversion due to lack of descriptors 
   support.

   (Request from Michael Thomas <mithomas@microsoft.com>
    from Microsoft ODBC team)

-- Added missed ROWS_FETCH_PTR status to SQLFetch and 
   SQLExtendedFetch as that of SQLFetchScroll along 
   with PARAMA_PROCESSED_PTR.

-- Fixed to not to set the default attributes for the 
   new DSN when the attributes are set through the config 
   APIs (Windows specific).

-- Added to return the DRIVER name when there is no DSN 
   is specified (Linux only).

-- Support for the new autoconf tools along with few 
   new configurations options.

-- Lot of cleanups to configure script to work on all 
   unix platforms along with gcc 3.x compatibility.

-- Added distribution uitlity scripts under scripts 
   sub-directory.

    * Binary distribution support for all platforms
    * Snapshot source distribution

-- Minor fix-ups to work with native compilers.

-- Lot of code cleanup.

Recommended upgrade to earlier versions on all 
platforms.

For complete changes, please refer to "ChangeLog" from :
http://www.mysql.com/downloads/api-myodbc-3.51.html
  
===============================================
3. OPEN ISSUES
===============================================
    
Some common problems:
--------------------
-- While performing Positioned updates or deletes or using 
   SQLSetPos with SQL_UPDATE or SQL_DELETE, and if there is 
   no Primary Key or UNIQUE NOT NULL column(s) exists in the 
   table, and if there is any duplicate rows without any 
   distinct field data, then there is no guarantee that the 
   driver will perform the requested operation on the correct 
   positioned row, instead it will operate on first duplicate
   row. 

-- Wrong connection port:  The port should be 3333 for MySQL 
   3.20 and 3306 (default) for MySQL 3.21 or newer.
   
-- If you are connecting to a server with a character set 
   that isn't compiled into the MySQL client library (the
   defaults are:
   latin1 big5 czech euc_kr gb2312 gbk sjis tis620 ujis) then 
   you need to install the mysql character definitions from 
   the charsets directory into the c:\mysql\share\charsets.
  
Known bugs:
----------
-- Access can't use float fields in a table without a timestamp 
   if you are going to update it. Double on the other hand should 
   work.
   
-- TIMESTAMP to TIME conversions doesn't work, when you are 
   converting from SQL_C_CHAR to SQL_TIME.
   
-- Binary fields are returned as strings, not as hex strings.

-- Some conversion are not according to the ODBC standard, but 
   this shouldn't affect standard applications.
   
-- ODBC can't support zero dates "0000-00-00". MyODBC automatically 
   converts 0000-00-00 dates to NULL.  Date columns that you want
   to update and that can be 0000-00-00 should not be declared as
   'NOT NULL'. 
   
-- From ADO:

   -  When using adUseServer cursor type, the rs.recordcount 
      will always return -1, where as using asUseClient should return 
      the correct value.

   -  Some times client side cursor type (adUseClient) generates
      error 'multi-step generated error' when performing result 
      set add, update or delete. But the same should work fine 
      when using server side cursor (adUseServer) from MyODBC 
      3.51.03 version.
   
-- When using the threaded applications on Windows, the DSN dialog 
   will show the handles leak when the dialog box is kept open. 
   Actually its not a leak, and these are freed when the dialog 
   box is closed. And this is how the MySQL handles the THREAD
   library.
   
-- When using the 'Dynamic Cursor Type' (OPTION=32), on large 
   tables, the performance will be a negative factor. So, unless 
   and absolutly required, don't use this flag.

================================================
4. TODO LIST
================================================

-- Support of Descriptors

-- Multi diagnostic status records. Currently driver
   supports single record i.e. application can only
   get the latest error or diagnostic information.
   
-- Support of keyset-driven cursor type.

-- Support of batch input parameter processing

-- Unicode API
================================================

For more information about the installation, setup, 
work-arounds, FAQ's, programming considerations, reporting 
bugs, and for many, please check:

http://www.mysql.com/products/myodbc/index.html



