On Jul 2, 2019, at 12:18 PM, Dom Latter <freeradius-users@latter.org> wrote:
On 02/07/2019 10:46, Dom Latter wrote:
I found / modified a small python script as below; again, no problem with "large" integers...
And again, with PHP, "SELECT 123456789" works fine but a large number gets an error from the ODBC driver.
SQLSTATE: 22003 Code: 1007 Message: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]The number '1000430295872340598237059823475034928750239875023948572309485' is out of the range for numeric representation (maximum precision 38).
That's all well and good, but what should *we* be doing differently? We're not Microsoft experts, or experts in ODBC. The ODBC layer was contributed by someone years ago, and we've maintained it since then. It mostly works, but new features require people who can delve into it and fix things. Alan DeKok.