Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-20106

Repository is aware of legacy storage specific ezcontentobject_tree.path_identification_string

    XMLWordPrintable

Details

    • Stetind Sprint 4, Stetind Sprint 5, Stetind Sprint 6

    Description

      Repository should not be aware of storage engine specifics. Awareness was added in: https://github.com/ezsystems/ezp-next/pull/145

      Several problems on moving all traces of this to legacy storage layer:

      • doing it without affecting performance
        • we need main language information not available in storage without additional querying
      • using SignalSlot for publishing aliases / plan for treating URL aliases as cache
        • can we treat path_identification_string as cache?

      What about simplified implementation eg. "location_2/location_5/location_42"?

      Attachments

        Activity

          People

            Unassigned Unassigned
            petar.spanja-obsolete@ez.no Petar Spanja (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 1 hour Original Estimate - 1 hour
                1h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 5 hours, 45 minutes
                1d 5h 45m