https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16056
Tomás Cohen Arazi <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Tomás Cohen Arazi <[email protected]> --- I think the right behaviour would be that Koha raises an error when trying to delete a record it is not on the DB. Hey, what would happen if we filter non-existent indexed records out, and then someone deletes "another" record in the meantime? The best approach is to make Koha handle this situations elegantly, instead of adding more and more latency to search results rendering. I vote for: render the deleted record, using Zebra's data as usual. Then show an error box if the user tries to delete it. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
