Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-684

Define what it means for an added property to conflict with an existing dynamic property

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.0_OS
    • Fix Version/s: V4.0_ERRATA01
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      [Applied]

    • Proposal:
      Hide

      It should be allowed to add a new prop/nav prop as long as any existing dynamic properties with that name are the same type, or derived from the same type, as the type defined for the new property. (Note: I was tempted to use "type-compatible" but I think that definition is a little too loose).

      Show
      It should be allowed to add a new prop/nav prop as long as any existing dynamic properties with that name are the same type, or derived from the same type, as the type defined for the new property. (Note: I was tempted to use "type-compatible" but I think that definition is a little too loose).

      Description

      Section 5.2 of Protocol currently says that adding properties/nav props are "safe" schema changes (not requiring a version change) as long as the added property/nav prop "does not conflict with an existing dynamic property".

      However, we don't say what "conflict" means.

        Attachments

          Activity

            People

            • Assignee:
              mikep Michael Pizzo
              Reporter:
              mikep Michael Pizzo
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: