Details

      Description

      This field (modified_subnode) has caused so much performance issues in the past, and should not be part of API, as stated by @<Gaetano Giunta> in #EZP-16340 this should be loaded lazily using a a dedicated function that does a SQL MAX() query, and not have to updated on every insert.

      So:

      • Remove from API (modifiedSubLocationDate), SPI (modifiedSubLocation) and REST, but verify that it is set in legacy storage engine internally

      Follow up step (when needed), add a function in SPI and API to get the mentioned info.

        Issue Links

          Activity

          Show
          Patrick Allaert (Inactive) added a comment - PR at: https://github.com/ezsystems/ezp-next/pull/139
          Hide
          Paulo Nunes (Inactive) added a comment -

          No QA needed

          Show
          Paulo Nunes (Inactive) added a comment - No QA needed

            People

            • Assignee:
              Unassigned
              Reporter:
              André Rømcke
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 5 hours, 25 minutes
                5h 25m