2017-02-26 15:49:31 +08:00
|
|
|
1) driver name comparison for MS SQL Server workaround is really kinda dirty
|
2000-03-17 03:08:22 +08:00
|
|
|
hack, but for now i don't know how to code it more carefully
|
|
|
|
|
2) another dirty hack: length of LONGVARCHAR and LONGVARBINARY fields is
|
|
|
|
|
currently set to MAX_ATTR_LEN. Maybe such fields must be handled with
|
|
|
|
|
SQLGetData() instead of SQLBindCol(), but it is said in documentation,
|
|
|
|
|
that it is guaranteed to work only when such column goes after last bound
|
|
|
|
|
column. Or should we get ALL columns with SQLGetData (then something like
|
|
|
|
|
_SQLFetchAsStrings() wrapper would do SQLGetData() for all columns)...
|
2000-09-06 02:16:58 +08:00
|
|
|
3) in some cases (particularly, when using OpenLink Generic ODBC driver with
|
2000-03-17 03:08:22 +08:00
|
|
|
MS SQL Server), it returns "Function sequence error" after all records are
|
|
|
|
|
fetched. I really don't know what it means, and after all
|
|
|
|
|
- it works with any other driver I tried
|
2000-09-06 02:16:58 +08:00
|
|
|
4) ldapsearch sometimes refuses to show some attributes ("NOT PRINTABLE" diags)
|
|
|
|
|
on Win32 (on linux everything's fine)
|
2000-10-26 05:23:04 +08:00
|
|
|
5) back-sql crashes on invalid filters (to be fixed ASAP)
|
2000-03-17 03:08:22 +08:00
|
|
|
|
