https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43407
--- Comment #4 from David Cook <[email protected]> --- (In reply to Mark Hofstetter from comment #3) > (In reply to David Cook from comment #2) > > It would also be useful for performance. We could have clustered databases > > with 1 writer and N readers, so read-only queries (especially ones for > > reports and other less time critical actions) could be done off the reader > > nodes instead of the writer node. > > > > This would make Koha much more horizontally scalable and robust. > > I think this has to be done on the database layer ie transparently for koha. > What I have in mind is separating concerns on the application layer like > users and permissions. You can do them in conjunction. After all, you're going to have to specify the user, so you specify your read-only user and use the read-only connection. (Depending on the context of course.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
