If a string ID is set for the integer id EndpointsAliasProperty, the getter should throw an exception about endpoints-proto-datastore HOT 2 OPEN

I'm actually in favor of leaving this as a Working As Intended.

Adding this extra code isn't fully necessary because:

• if they are using the getter, they will likely have used the setter (or this will have been done by library code) and the setter won't allow a bad value
• the protorpc part of the request will fail if the value is the wrong type
• if they set the value using the key rather than the setter, it's not likely they will use the getter, hence only the translation to protorpc message code will call the getter

_{NOTE: THIS POST WAS EDITED AFTER BEING MIGRATED.}

_{Code Hosting Comment Metadata:
author.htmlLink=https://code.google.com/u/[email protected]/
author.name=[email protected]
id=2
published=2013-02-18T05:11:02.000Z}

from endpoints-proto-datastore.

Having entities with a mixture of int and string ids is not all that uncommon IMO.

I've seen several cases where customers have existing entities with numeric (auto assigned ids) and decide to start using string ids (to defeat poor sharding behavior when using auto ids).

_{NOTE: THIS POST WAS EDITED AFTER BEING MIGRATED.}

_{Code Hosting Comment Metadata:
author.htmlLink=https://code.google.com/u/[email protected]/
author.name=[email protected]
id=3
published=2013-02-28T01:50:55.000Z}

from endpoints-proto-datastore.