4 Jul
2019
4 Jul
'19
2:21 p.m.
> On 4 Jul 2019, at 11:10, Dom Latter <freeradius-users@latter.org> wrote: > > > On 03/07/2019 07:53, Alan DeKok wrote: >> On Jul 2, 2019, at 6:21 PM, Dom Latter <freeradius-users@latter.org> wrote: >>>> That's all well and good, but what should *we* be doing differently? >>> >>> Well, if I knew that... >> That is the problem. >> As background, the unfortunate thing is that the FreeRADIUS core team is pretty darn small (less than 5, by a lot.) And we're expected to be experts in: >> * RADIUS > > > <snip> > > Yes, it's a lot of stuff. > > Anyway, I have run ltrace to grab calls to the MS ODBC driver, from both > freeradius and a small python test script (which doesn't exhibit this > weird bug). > > These are the calls (sorted alphabetically) that are used by Freeradius: > > SQLAllocHandle > SQLBindCol > SQLDisconnect > SQLFetch > SQLFreeStmt > SQLNumResultCols > SQLSetEnvAttr > > > And these are the ones used by Python: > > SQLAllocHandle > SQLDescribeColW > SQLDisconnect > SQLEndTran > SQLExecDirectW > SQLFetch > SQLFreeHandle > SQLFreeStmt > SQLGetData > SQLNumResultCols > SQLRowCount > SQLSetConnectAttr > Could we get the calls listed chronologically. -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2