[Koha-bugs] [Bug 7806] Don't use 0000-00-00 to signal a non-existing date

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7806

Marcel de Rooy <m.de.rooy at rijksmuseum.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Signed Off                  |Passed QA

--- Comment #19 from Marcel de Rooy <m.de.rooy at rijksmuseum.nl> ---
Although this looks quite good to me, it is really hard to be convinced that
all appearances of 0000-00-00 in the data now are caught correctly by the
codebase.

I found at least one issue (no blocker):
select count(*) from items where dateaccessioned= '0000-00-00';
+----------+
| count(*) |
+----------+
|      335 |
+----------+
1 row in set (0.12 sec)
This comes from a production database.
So I tested with an item. Set dateaccessioned to 0*. Open item editor. You see
the 0* on the form. Tab thru the field so that the date gets FOCUS. This will
update the 0* in the old situation, but not in the new one (obviously).
Note that the CLICK event uses the force parameter and will set the date.

Could you add this one to the atomicupdate too?
And please provide me some evidence that we found the last case ;) For instance
by checking date columns in a larger production database being used for a
longer time..

PQA for now.

-- 
You are receiving this mail because:
You are watching all bug changes.