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

Specify a api to field types for dealing with relation handling

    XMLWordPrintable

Details

    • Stetind Sprint 1, Stetind Sprint 2, Stetind Sprint 3, Stetind Sprint 4, Stetind Sprint 5, Stetind Sprint 6

    Description

      Based on the code produced in #EZP-20034 find a way to create a low level interface to be able to reuse code across fieltypes for relations.

      ...

      Some background:

      All relations are stored using ezcontentobject_link table, with some specifics.

      Object level relations

      In legacy storage object level relations from one content object to a same other content object are merged into single DB row, using ezcontentobject_link.relation_type as a bitmask.

      There are three types of relations on object level: common, XML link and XML embed. Common type relations are created manually, while XML link and XML embed type relations are created automatically whenever an internal link or embed tag is created inside XML text field of a content object. For this reason object level relations are not added and removed directly, but through adding rows into ezcontentobject_link table with special op codes, which are processed when content is published.

      Attribute level relations

      There is only one type of attribute level relations: (obviously) attribute type relations. Thus attribute type relations are never merged using bitmask, also they are manipulated direcly (op codes are not used).

      Attachments

        Activity

          People

            Unassigned Unassigned
            andre.romcke-obsolete@ez.no André Rømcke (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2 days Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week, 2 days, 4 hours, 55 minutes
                1w 2d 4h 55m