Skip to content
This repository was archived by the owner on Dec 8, 2022. It is now read-only.

we need to support string based keys, not just integer based ids #21

Closed
dhermes opened this issue Apr 24, 2013 · 1 comment
Closed

we need to support string based keys, not just integer based ids #21

dhermes opened this issue Apr 24, 2013 · 1 comment

Comments

@dhermes
Copy link
Contributor

dhermes commented Apr 24, 2013

It's quite common for developers to use string based keys rather than integer based keys. There needs to be a way for an EndpointsModel to incude the string based key over the wire.

Right now, _message_fields_schema can include 'id' in the list of fields, as a way to have integer based keys included on the wire. I suggest allowing 'string_id' and 'int_id'. Alternatively, perhaps one could specify 'key', which would cause an ndb.KeyProperty to be passed on the wire. This KeyProperty would contain either an int key or a str key.

NOTE: THIS POST WAS EDITED AFTER BEING MIGRATED.



Code Hosting Comment Metadata:
author.htmlLink=https://code.google.com/u/fredsa/
author.name=fredsa
id=0
published=2013-01-26T20:13:19.000Z

Code Hosting Issue Metadata:
published=2013-01-26T20:13:19.000Z
stars=2
updated=2013-01-26T20:13:19.000Z
originalIssue=https://code.google.com/p/endpoints-proto-datastore/issues/detail?id=39
author=@fredsa
owner.htmlLink=

@dhermes
Copy link
Contributor Author

dhermes commented Jun 6, 2013

Closing as duplicate of #74

@dhermes dhermes closed this as completed Jun 6, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant