Why email, username, postal code, etc. Are objects in the GAE data warehouse

I saw that there are so many objects in the GAE datastore that at the end of the line are at least visible.

List of Java GAE Data Warehouse Objects

I would like to know the reason for this? indexing? semantic search?

+4
source share
2 answers

I had the same question a couple of years ago. Nick answered him here . Java classes provide parity with Python, and in Python this is useful for the special behavior of .to_xml (). It is possible that when GAE receives the correct GEO requests, GeoPt may become useful, but otherwise you can ignore them.

+5
source

Itโ€™s completely clear to me - the question is what we (Google App Engine designers) thought about adding these โ€œsemanticโ€ types of properties.

Then I was not in the team, but I think that we were in love with the automatic generation of XML from objects using the ATOM scheme. I do not think it is very popular or useful in practice. You can ignore them - their check is trivial (should not be empty).

In NDB (the new Python client for the data warehouse), I decided not to support these semantic property types or XML generation, and so far only one person has requested it: http://code.google.com/p/appengine-ndb-experiment/issues/ detail? id = 96

+9
source

Source: https://habr.com/ru/post/1402775/


All Articles