https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42508
--- Comment #16 from Tomás Cohen Arazi (tcohen) <[email protected]> --- (In reply to Mark Hofstetter from comment #9) > Most of the opinions about database triggers seem a little outdated to me. Fair enough, and I agree modern MariaDB/MySQL capabilities are much better than they used to be. My concern is less about triggers being inherently bad technology, and more about where we want patron indexing/search materialization logic to live long-term in Koha, especially considering imports, background jobs, plugins, upgrades, and high-concurrency circulation workflows. I think there is probably room for both approaches here: * SQL materialization for simpler deployments; * Elasticsearch for more advanced search capabilities and larger installations. What I would really like to avoid is duplicating indexing/update logic in multiple places. If we can converge on a shared async indexing/materialization framework, different backends could coexist much more cleanly. -- 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/
