[dbfpy-devel] [ dbfpy-Bugs-1731650 ] Real use problems.

[SourceForge.net <no...@so...>]

Bugs item #1731650, was opened at 2007-06-05 12:53
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=746843&aid=1731650&group_id=140566

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Real use problems.

Initial Comment:
I found a few problems while converting dbf files to SQL.

1. class DbfNumericFieldDef, method decodeValue returns int or float, float is a problem cause Numeric field is accurate, but float is floating point. Some old financial systems use Numeric fields to keep monetary data.

2. class DbfCurrencyFieldDef, method decodeValue returns float. It's questionable, just as above.

I worked around above problems by changing decodeValue method, so that Numeric and Currency fields return string value.

3. class DbfDateTimeFieldDef, method decodeValue fails on Python 2.5, on Windows. there is problem (exception) in line:
_rv += datetime.timedelta(0, _msecs / 1000.0)
It started to work when I changed it to
_rv += datetime.timedelta(0, _msecs // 1000.0)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=746843&aid=1731650&group_id=140566