Support keyless entities for singletons

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_WD01
    • Affects Version/s: V4.0_ERRATA02
    • Component/s: None
    • None
    • Environment:

      [Proposed]

    • Hide

      Relax the requirement that only abstract entity types aren't required to have keys, but require that any entity type used in a collection must have a key.

      Allow a singleton or single-valued containment navigation property to use a type without having to define an arbitrary/meaningless key property.

      It is a breaking schema change to add/modify/remove a key in an entity definition.

      Show
      Relax the requirement that only abstract entity types aren't required to have keys, but require that any entity type used in a collection must have a key. Allow a singleton or single-valued containment navigation property to use a type without having to define an arbitrary/meaningless key property. It is a breaking schema change to add/modify/remove a key in an entity definition.
    • Show
      https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59031/odata-csdl-xml-v4.01-wd01.docx

      Entity types that are used for singletons, or targets of a single-valued containment navigation property, don't need keys. Keys are only required when accessing an entity within a collection.

      We could consider relaxing the requirement that entity types used exclusively for singletons/single-valued containment nav props have keys. We would have to carefully think through the ramifications of doing this, but they should always be able to be accessed through their canonical URL without a key.

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

              Created:
              Updated:
              Resolved: