Bug 15683 - Inconsistent population of lastreneweddate between AddRenewal and AddIssue
Summary: Inconsistent population of lastreneweddate between AddRenewal and AddIssue
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: 3.20
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-27 17:40 UTC by Barton Chittenden
Modified: 2021-05-12 16:24 UTC (History)
7 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barton Chittenden 2016-01-27 17:40:44 UTC
When lastreneweddate is populated via C4::Circulation::AddRenewal, it is added as a date, whereas C4::Circulation::AddIssue stores it as DateTime, i.e. hours, minutes and seconds are populated.

Because of hourly loans, I think that it only makes sense to store lastreneweddate as a full datetime.