A while ago I reported these errors in fpdb-errors:
Code:
D:\tools\fpdb.41\Database.py:2324: Warning: Data truncated for column 'rakeDealt' at row 49
D:\tools\fpdb.41\Database.py:2324: Warning: Data truncated for column 'rakeContributed' at row 49
D:\tools\fpdb.41\Database.py:2324: Warning: Data truncated for column 'rakeWeighted' at row 49
The columns mentioned just contain 0 whenever rake is < 1 dollar.
(I'm using MySQL, with session cache enabled)
I changed the data type from Decimal(10,0) to Double. This has so far eliminated the warnings, however when bulk importing data, the following occurred:
Code:
2017-03-01 07:50:15,665 - importer ERROR Importer._import_hh_file: '<type 'file'>' Fatal error: ''Traceback (most recent call last): File "Z:\\fpdb\\build\\fpdb\\out00-PYZ.pyz\\Importer", line 477, in _import_hh_file File "Z:\\fpdb\\build\\fpdb\\out00-PYZ.pyz\\Hand", line 350, in updateSessionsCache File "Z:\\fpdb\\build\\fpdb\\out00-PYZ.pyz\\Database", line 2836, in storeSessionsCacheTypeError: unsupported operand type(s) for +=: \'float\' and \'Decimal\'''
I also tried Decimal(X,Y) with various X's and Y's, but although they all give
non-zero values for the affected columns, the warnings persist.
Questions:
- Is there a way to have fpdb-errors closed after each write -- or at least flush the buffer?
When fpdb.exe crashes hard, anything not written is lost.
- Is there a switch to cause more verbose logging?
Quote:
Originally Posted by phil_r
Thanks -- I upgraded to 64-bit python 2.7, and installed PyQt5.
Now, instead of complaining the Qt5 is missing, when I try to run run_fpdb.py the is a brief flicker. No windows, no error messages, no logging no nuttin'
Cheers,
--D