https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30888
--- Comment #15 from Marcel de Rooy <[email protected]> --- Please read this on dba.stackexchange.com: https://dba.stackexchange.com/questions/14402/tombstone-table-vs-deleted-flag-in-database-syncronization-soft-delete-scenari/14419 It contains questions like: How fast do deletes need to be? How fast do un-deletes need to be? How often will deleted data be queried and will it be queried with data that has not been deleted? How fast do queries of deleted data need to be? Do you need to preserve only deleted items or changes as well? Do you need to keep the table/indexes on the primary table small? What partitioning and/or change tracking technologies are available on the database platform? How much disk space is available? Will the deleting occur on the fly or in batch operations? In this authorities case, deletes are not required to be very fast. And we are not undeleting right now. The deleted data is not queried often. We do not preserve all changes. There is no need to keep all indexes on deleted data (I removed one here as well). So I would tend (as objective as I can..) to the tombstone table here for performance reasons. (And less code as argued already.) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
