[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-59) Literal value "Max" for MaxLength attribute is missing
[ http://tools.oasis-open.org/issues/browse/ODATA-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-59: ---------------------------- Proposal: Add literal "Max" as a shorthand for "maximum length supported by the server" for Edm.Binary, Edm.Stream and Edm.String. Environment: [Proposed] > 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 > Environment: [Proposed] > 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]