You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 8, 2022. It is now read-only.
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.
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 anndb.KeyProperty
to be passed on the wire. ThisKeyProperty
would contain either anint
key or astr
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=
The text was updated successfully, but these errors were encountered: