© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
We've gotten reports of this on our 3.2.4 system. I'll test the patch, but here's a question:
Why do we retain current_copy in a cancelled hold?
The two examples I saw in our production system were situations where a cancelled hold existed with the same current_copy as the item that was on the holds shelf for a current ready for pickup hold.
Our production system has 414,000 cancelled holds with current_copy set. About 367,000 of these do NOT have a NULL capture_time.