问题描述
具有带有整数字段的Cloud Endpoints(ProtoRPC)消息类，例如
Having a Cloud Endpoints (ProtoRPC) message class with an integer field, e.g.
TestMsg(messages.Message):
int_field = messages.IntegerField(1)
和方法:
@endpoints.method(VoidMessage, TestMsg)
def test_int_field():
return TestMsg(int_field=1234567890123)
在本地开发服务器上的JSON响应导致:
On local dev server JSON response results in:
{ int_field: 1234567890123 }
在生产中，由于某种原因，数字被转换为字符串:
Whereas in production the number gets converted to a string for some reason:
{ int_field: "1234567890123" }
对于较小的数字，整数似乎并没有转换为字符串.
For smaller numbers integers don't seem to be converted to strings though.
这是预期的行为吗?任何人都可以复制吗? (以防万一:我正在欧盟数据中心中运行此代码)
Is this expected behaviour? Anyone can repro? (In case it matters: I'm running this code in EU datacenters)
推荐答案
我猜@proppy是正确的.另外，它以发现格式明确指出
I guess @proppy is right. Also, it clearly states in the discovery format that
和
所有其他类型的int/bigint/任何值都表示为具有不同格式的字符串"类型.更多信息: https://developers.google.com/discovery/v1/type-format
All other kinds of int/bigint/whatever values are repesented as "string" types with different formats. More info: https://developers.google.com/discovery/v1/type-format
因此，1234567890123数字实际上不能以整数"类型表示.只是开发服务器不会自动将整数转换为字符串(就像生产基础结构一样)，而且我没有意识到在本地测试时该数字有多大.
So, 1234567890123 number cannot in fact be represented in "integer" type. It's just the dev server doesn't convert integers to strings automatically (like the production infrastructure does), and I didn't realize how big the number was while testing locally.
事实证明，Google的一个团队已经在努力使其保持一致: https://code.google.com/p/googleappengine/issues/detail?id=9173
It turns out a team at Google is already working on making it consistent: https://code.google.com/p/googleappengine/issues/detail?id=9173
这篇关于IntegerField值已转换为某些数字的字符串的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！