Recursive complex types must be nullable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.01_ERRATA01
    • Affects Version/s: V4.01_OS
    • Component/s: CSDL JSON, CSDL XML
    • None
    • Hide

      Clarify that a recursive single-valued navigation and complex typed property must be nullable.  This rule is implied today, so calling it out to make it more apparent should not be a breaking change.

      Show
      Clarify that a recursive single-valued navigation and complex typed property must be nullable.  This rule is implied today, so calling it out to make it more apparent should not be a breaking change.
    • Show
      https://github.com/oasis-tcs/odata-specs/pull/227

      We have rules around a partner navigation property in a recursive containment relationship (it must be single valued and nullable) but we don't call out the fact that the child of a single-valued recursive containment must also be nullable (or the recursion would never end). 

      Similarly, we say nothing about the child of a recursive complex-typed property. For example, we don't have a rule against the following definition, although the model it describes results in an endless recursion:

       

      <ComplexType Name="myType">
          <Property Name="nested" Type="myType" Nullable="false">
      </ComplexType> 

       

            Assignee:
            handl
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: