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
Hello, i am using gcloud's datastore library and stumble into a strange problem. When i query on an entity that has a double value property without precision (ie 1.00, 2.00) , the following exception is thrown.
You appear to be using package:gcloud/src/datastore_impl.dart (which internally is based upon package:googleapis/datastore/v1.dart which uses a JSON based api). So it appears that the query result returned by the server does not encode the double value as a doubles in the JSON response but rather as integers if it's a whole number (javascript does not know the difference either).
If at all, it is a bug in the discoveryapis_generator, but the schema actually specifies it is a double value (see schema). Maybe we should move the issue over there - it could probably be fixed by calling toDouble() on values returned from the server which are specified to be of type double.
Longer term we will not be using the json-based API anymore.
The package:appengine is using internally a gRPC-based implementation of datastore. Are you using the package:appengine?
Hello @mkustermann and thank you for your detailed reply.
After some research, me and a colleague of mine found out about the gRPC-based implementation of datastore that exists inside the appengine and decided to give it a try. It worked.
Long story short, we have implemented a rest api written in dart that runs on googles container engine and my question is , is it safe to use the gRPC-based implementation of datastore in production?
Hello, i am using gcloud's datastore library and stumble into a strange problem. When i query on an entity that has a double value property without precision (ie 1.00, 2.00) , the following exception is thrown.
I have created an example of the behavior HERE
The text was updated successfully, but these errors were encountered: