[Koha-bugs] [Bug 23185] New: Koha::Objects supports passing through 'update' which means we can side step 'set' + 'store'

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23185

            Bug ID: 23185
           Summary: Koha::Objects supports passing through 'update' which
                    means we can side step 'set' + 'store'
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: critical
          Priority: P1 - high
         Component: Architecture, internals, and plumbing
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: martin.renvoize at ptfs-europe.com
        QA Contact: testopia at bugs.koha-community.org
                CC: dcook at prosentient.com.au,
                    jonathan.druart at bugs.koha-community.org,
                    koha-bugs at lists.koha-community.org,
                    kyle at bywatersolutions.com, m.de.rooy at rijksmuseum.nl,
                    martin.renvoize at ptfs-europe.com,
                    testopia at bugs.koha-community.org, tomascohen at gmail.com
        Depends on: 21761
  Target Milestone: ---

+++ This bug was initially created as a clone of Bug #21761 +++

If we're adding triggers at the code level all over the place by overloading
the store method we need to never ever let dbic handle it.. by allowing the
'update' method through we are exposing ourselves to places in the codebase
skipping the store triggers.

This would in effect bind us to the 'update_all' style of update call from
dbic, which results in a loop over the affected rows so that in code triggers
can be called per row rather than allowing any form of 'update all these rows
to X' in one query.


Referenced Bugs:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21761
[Bug 21761] Koha::Object supports passing through 'update' which means we can
side step 'set' + 'store'
-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
You are on the CC list for the bug.