Perhaps I'm missing something but query.h call setprecision it in four
places.
The thread below from April of last year lead us to submitting a patch
to fix it when it was too low for double. Perhaps it simply needs to be
bumped up.
http://lists.mysql.com/plusplus/7549
-----Original Message-----
From: Ken Smith [mailto:kenwsmith@stripped]
Sent: Wednesday, March 25, 2009 5:50 AM
To: plusplus@stripped
Subject: RE: inserts, strings and setprecision
I've tested the precision, and MySQL++ doesn't set it automatically. I
had to force it using setprecision. I commented out any code that uses
ostream just to make sure it wasn't being set elsewhere.
