When does objectify verify existing data in a related entity? -
I am writing this with my head now, tell me wrong if I am wrong but I remember the following code verification It is done that if the unit behind the reef-object is & gt; Actually exists:
Ref & lt; User & gt; the user; // We have a reference field for any other entity, public zero reference user (long user ID) {key < Users & gt; Key = key.create (User.class, userId); // This is a protobbut, and no DB access is like this. User = create referee (key); // It appears that if an existing record is present, and if it is not, then it fails? }
What if the ref & lt;> area is already set during an update? Is it true that it is not verified again if the record still exists?
I clarify that when the object ensures data integrity and when it is not referenced whether a referenced record exists or not.
The objective does not ensure the relevance of any type of integrity nor low-level API.
The referee objects are just some objects, which are slightly more behavior (most importantly found) (method) (method).
Comments
Post a Comment