[OASIS Issue Tracker] (ODATA-874) Allow Edm.String as underlying type for enumeration types

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

    [ https://issues.oasis-open.org/browse/ODATA-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61137#comment-61137 ] 

Mark Stafford commented on ODATA-874:
-------------------------------------

I'm not sure I understand the advantage to what you're proposing here. Such a data source could simply not attach values to the enum members and effectively ignore that the underlying type is Edm.Int32. As far as I can tell, there's not a clear limitation we are imposing on these data sources. Yes, there's a bit of a gap but if we close that gap, we open it on the code generation end of the equation.

> Allow Edm.String as underlying type for enumeration types
> ---------------------------------------------------------
>
>                 Key: ODATA-874
>                 URL: https://issues.oasis-open.org/browse/ODATA-874
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: OData CSDL
>    Affects Versions: V4.0_ERRATA03
>            Reporter: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> While using non-negative integers for flag enum types is natural, some data sources support enumeration types that use strings as the underlying type.
> This was also raised in https://issues.apache.org/jira/browse/OLINGO-803.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)