Consider deprecating symbolic "max" length

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_CSD02
    • Affects Version/s: V4.0_ERRATA03
    • Component/s: CSDL XML
    • None
    • Environment:

      Applied

    • Hide

      The OData 4.0 use of the symbolic value max in place of an integer value is deprecated in OData 4.01. While OData 4.0 clients MUST be prepared for this value, OData 4.01 and greater services MUST NOT return a value of max for the MaxLength attribute and MAY instead specify the concrete maximum length supported for the type by the service, or omit the attribute entirely.

      Show
      The OData 4.0 use of the symbolic value max in place of an integer value is deprecated in OData 4.01. While OData 4.0 clients MUST be prepared for this value, OData 4.01 and greater services MUST NOT return a value of max for the MaxLength attribute and MAY instead specify the concrete maximum length supported for the type by the service, or omit the attribute entirely.
    • Hide

      https://www.oasis-open.org/committees/download.php/60254/odata-csdl-xml-v4.01-wd02-2017-03-10.docx

      Show
      https://www.oasis-open.org/committees/download.php/60254/odata-csdl-xml-v4.01-wd02-2017-03-10.docx

      We currently allow specifying "max" as the maximum length of a string property. This is of dubious value, and we don't want to support it in the JSON format. Should we deprecate it from the XML format?

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

              Created:
              Updated:
              Resolved: