Issue 1119 in gbif-providertoolkit: Improve handling of date 0000-00-00 in MySQL

[gbif-provi...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement

New issue 1119 by ammat...@gmail.com: Improve handling of date 0000-00-00
in MySQL
https://code.google.com/p/gbif-providertoolkit/issues/detail?id=1119

What feature would like to see being added to the IPT?

Handling of the invalid date 0000-00-00 from MySQL is a very known problem,
and there are ways to create queries to transform or ignore these date
cases (so it is understandable why issue 819 was a won't fix). However,
this is such a common problem that seem worth while handling the exception
in IPT to convert these occurrences to empty values (similar to the fact
that nulls are interpreted as empty when generating the CSV).
When dealing with large datasets, we learn about these occurrences only
after the whole archive processing phase finishes and since this could take
a while, this becomes a laborious process.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[gbif-provi...@googlecode.com]

Comment #1 on issue 1119 by kyle.br...@gmail.com: Improve handling of date

0000-00-00 in MySQL
https://code.google.com/p/gbif-providertoolkit/issues/detail?id=1119

Please be aware this issue has been moved to GitHub:
https://github.com/gbif/ipt/issues/1119 Any work on this issue will be
reported there from now on.