http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9011
Kyle M Hall <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Signed Off --- Comment #121 from Kyle M Hall <[email protected]> --- (In reply to Jonathan Druart from comment #119) > (In reply to Kyle M Hall from comment #115) > > As far as I can tell there is no way around this. I tried to use a left join > > but you cannot use a group by in an update statement. > > Kyle, > Just a quick thought: wouldn't it be possible to execute another update > statement after the existing one, instead of adding complexity to it? I do not believe this is possible. The addition isn't adding additional changes, it's *preventing* additional changes. We can't create a second query that prevents updates caused by the first one. I think we have only two choices here, either accept the speed cost or switch back to the original version. I have no problem with either choice, but one must be made. We can't hold this feature in discussion forever. This is not complicated as a choice, especially since it seems that the speed cost is unacceptable. -- 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/
