1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
|
*********************************************************
* MySQL ODBC 3.51 Driver *
* RELEASE NOTES *
* *
* Version: 03.51.06 (Stable) Updated : 27 Feb 2003 *
* (C) Copyright MySQL AB 1995-2004 *
*********************************************************
================================================
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 stable release of Connector/ODBC 3.51.06;
and which has minor bug fixes for the 3.51.05 version.
The new development of Connector/ODBC is started in
3.52 tree which mainly aims to support the following
features:
- Binary protocol compatible with MySQL 4.1 to improve
the performance.
- Missed features from 3.51 (descriptors)
- Array parameter handling
- Unicode API
================================================
2. BUG FIXES
================================================
3.51.7
-- Use MyODBC with 4.0 client library
-- Fix configure to take options from mysql_config.
Now one only have to supply --with-mysql-path instead of
--with-mysql-libs and --with-mysql-includes
This also fixes linking problems with libraries like ssl
-- Fix compiler warnings
-- Compile thread safe library as default
-- Disable sigpipe if not compiling threadsafe
-- Test are now run with users 'odbc', password ''
-- Big code cleanup to make the code (more) conformant to MYSQL coding
conventions
-- Fixed a crash when SQLSetPos is called with SQL_ADD to insert
a record with empty value i.e. when pcbValue is SQL_COLUMN_IGNORE
-- Fixed SQLFetch to return and update SQL_ATTR_ROWS_FETCHED_PTR and
SQL_ATTR_ROW_STATUS_PTR statement attribute pointers appropriately
-- Fixed SQLFetch to take care SQL_ROWSET_SIZE correctly.
-- Added internal MyODBC test library under 'test' directory
-- Added bin-tar to Makefile.am to generate the binary distro directly
-- Added make_win_src_distribution.sh to scripts/ to generate Windows
source archieve.
-- Source code structure change to take care of Windows files and its
Makefiles separately into 'win32' directory.
-- Fix for .NET crash when creating the MFC database project (BR #913)
-- Added search pattern for all catalog APIs for all input parameters
(Catalog, Table and Column names) (back port feature from 3.52).
-- Added the support of SQLProcedures when talking with MySQL 5.0
(back port feature from 3.52).
-- Fixed SQL_ATTR_CURRENT_CATALOG to take correct length pointer.
-- Portability fixups while using the platform dependant compilers
The following list of bug reports from http://bugs.mysql.com, has
been fixed or addressed in this release (TODO: add all reports):
913, 1102
Recommended upgrade to all earlier versions of MyODBC on
all platforms.
For complete changes, please refer to "ChangeLog" from :
http://www.mysql.com/downloads/api-myodbc-3.51.html
===============================================
4. 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.
================================================
5. 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
|
