[OASIS Issue Tracker] Updated: (ODATA-59) Literal value "Max" for MaxLength attribute is missing

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/ODATA-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-59:
----------------------------

    Resolution: 
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46811/odata-csdl-v1.0-wd01-2012-09-03-RH.doc

Accepted: https://www.oasis-open.org/committees/download.php/46845/odata_meeting-6_on-20120906_minutes.html

  was:https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46811/odata-csdl-v1.0-wd01-2012-09-03-RH.doc


> Literal value "Max" for MaxLength attribute is missing
> ------------------------------------------------------
>
>                 Key: ODATA-59
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-59
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL v1.0
>    Affects Versions: WD01
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>            Priority: Minor
>             Fix For: WD01
>
>
> Add the literal "Max" as a possible value for the MaxLength attribute, and define its meaning for properties of type
>  - Binary
>  - Stream
>  - String
> The old default of Max == 2^31 is probably wrong: should be 2^31-1 if signed Int32, but why limit it to that value in the age of 64-bit operating systems?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira