1 1) driver name comparison for MS SQL Server workaround is realy kinda dirty
2 hack, but for now i don't know how to code it more carefully
3 2) another dirty hack: length of LONGVARCHAR and LONGVARBINARY fields is
4 currently set to MAX_ATTR_LEN. Maybe such fields must be handled with
5 SQLGetData() instead of SQLBindCol(), but it is said in documentation,
6 that it is guaranteed to work only when such column goes after last bound
7 column. Or should we get ALL columns with SQLGetData (then something like
8 _SQLFetchAsStrings() wrapper would do SQLGetData() for all columns)...
9 4) in some cases (particularly, when using OpenLink Generic ODBC driver with
10 MS SQL Server), it returns "Function sequence error" after all records are
11 fetched. I really don't know what it means, and after all
12 - it works with any other driver I tried
13 5) referral handling. this bug actually addresses all backends, as I can
14 understand. draft-ietf-ldapext-namedref-xx.txt says that referral should be
15 returned for ANY object containing "ref" attribute. And is_entry_referral
16 macro designed for "referral" objectclass only. This limits usability of
17 referrals too much. For instance, I could want to replicate some subtree on
18 another server, storing just "searchable" attributes + referral to full
19 object, and then use this subtree as kind of index for query routing.
20 If search returns referrals only for "referral" entries - I cannot do such
22 6) DO NOT EVER USE -O2 option (or any other optimization) under Un*x/gcc!!!
23 I have spent days trying to catch weird bugs, which went gone with optimization off
24 7) The same thing that works on RedHat 6.0 (glibc 2.1.1), dumps core on
25 6.1 (glibc 2.1.2) (the same code behaves differently when built on 6.0 and 6.1)
26 my problem was solved by upgrading iODBC to 3.0 beta - but it is kinda strange
27 that beta works better than release (and release still works fine on 6.0)
28 9) ldapsearch sometimes refuses to show some attributes ("NOT PRINTABLE" diags)
29 on Win32 (on linux everything's fine -- at least with mySQL)