[dbfpy-devel] [ dbfpy-Bugs-1656884 ] Bad dbf date field strings

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

Bugs item #1656884, was opened at 2007-02-10 20:31
Message generated for change (Comment added) made by a1s
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=746843&aid=1656884&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: Drew Ferguson (blacktav)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bad dbf date field strings

Initial Comment:
Hi

Thanks for a life-saver project

An application I have (SwissPerfect) stores bad date strings formatted with spaces including incomplete dates (eg year only).

Attached is a diff on utils.py 2.1.0 with a function to parse such bad date strings and fix them

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

>Comment By: alexander smishlajev (a1s)
Date: 2007-02-10 21:03

Message:
Logged In: YES 
user_id=8719
Originator: NO

thank you for reporting it.  it's a +1 for the plan to make the Dbf class
to optionally ignore all conversion errors, as i said in
https://sourceforge.net/mailarchive/message.php?msg_id=37890707

however, i am not given to "fix" invalid values by replacing missing date
parts by an arbitrary number.  perhaps returning None instead of invalid
dates would be more consistent...

i have checked in a quick fix allowing date strings to have leading spaces
instead of zeroes.  if that solves your problem, i will release new dbfpy
version as soon as possible.


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

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