Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SQL Server money precision must be 4

See original GitHub issue

Python: 3.7.0
pyodbc: 4.0.24
OS: Linux
DB: Microsoft SQL Server 2008 R2 (SP3) - 10.50.6220.0 (X64)
driver: FreeTDS

db = pyodbc.connect(my_connection_string)
sql = 'SELECT CAST(0.1234 AS money)'
print(db.execute(sql).fetchall()[0]) 

# outputs (Decimal('0.12'), )
# expected (Decimal('0.1234'), )

All MSSQL versions should have 4-digits precision for money type

Is this configurable maybe? Thank you!

Issue Analytics

State:
Created 5 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

studentikscommented, Sep 24, 2018

Oh my, hope it’s in the right place now )

1reaction

v-chojascommented, Sep 24, 2018

		Entry:
			Statement = 0x5606ab1f2f30
			Column Number = 1
			Target Type = -8 SQL_WCHAR
			Buffer Length = 4096
			Target Value = 0x5606ab219380
			StrLen Or Ind = 0x7ffcdd9b4a20
[ODBC][32335][1537818877.979645][SQLGetData.c][545]
		Exit:[SQL_SUCCESS]                
			Buffer = [0.12](unicode)                
			Strlen Or Ind = 0x7ffcdd9b4a20 -> 8

This is fault of ODBC driver, not pyODBC. pyODBC is asking driver to return result in character format and driver is returning character string “0.12” which has truncated the precision already.