https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30888
--- Comment #23 from Martin Renvoize <[email protected]> --- So I stayed pretty quiet in the developer meeting around this topic to be honest. I still don't feel hugely knowledgable about the topic now, but my general feeling has changed over the years around this sort of topic. Whilst I can see the advantages of a single table, I can also see the advantages of tombstone tables.. and in fact I think they both have their place in Koha. My feeling was that we agreed that generally we'd push for combined tables for Koha whenever appropriate, but I don't think we should rule out tombstones when they make sense for performance and code simplicity reasons. In this particular case, I'd actually push for the pragmatic solution of taking the code that's written. It follows some solid patterns we already have whilst also being reasonably modern in it's approach. Personally, I'd prefer to see this move and be accepted rather than have it die. -- You are receiving this mail because: You are the assignee for the bug. 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/
