blocks|key|4029722|text|正如您可能在Node.js+(和Javascript)+SDK的文档中看到的那样，无论是使用DocumentReference的方法还是CollectionReference的方法，这都是不可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4029723|更准确地说，DocumentReference的set()和update()方法都返回一个包含void的Promise，而CollectionReference的add()方法返回一个包含DocumentReference的Promise。|style|CODE|4029724|4029725|附注(与下面darrinm的回答一致)：有趣的是，使用Firestore+REST+API时，当您create+a+document时，您会得到一个Document对象(即通过API端点响应)。|4029726|entityMap|0|LINK|mutability|MUTABLE|url|https://firebase.google.com/docs/reference/js/firebase.firestore.DocumentReference|1|https://firebase.google.com/docs/reference/js/firebase.firestore.CollectionReference|2|3|https://firebase.google.com/docs/reference/js/firebase.firestore.DocumentReference#set|4|https://firebase.google.com/docs/reference/js/firebase.firestore.DocumentReference#update|5|6|https://firebase.google.com/docs/reference/js/firebase.firestore.CollectionReference#add|7|8|https://firebase.google.com/docs/firestore/reference/rest|9|https://firebase.google.com/docs/firestore/reference/rest#rest-resource:-v1.projects.databases.documents|10|https://firebase.google.com/docs/firestore/reference/rest/v1/projects.databases.documents#Document^0|1A|H|0|1W|J|1|0|O|5|U|8|1B|4|29|5|6|H|2|O|5|3|U|8|4|1P|J|5|29|5|6|2M|H|7|0|0|22|8|R|I|8|1D|H|9|22|8|A|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@$A|1A|B|1B|1|1C]|$A|1D|B|1E|1|1F]]|C|$]]|$1|D|3|E|5|6|7|1G|8|@$A|1H|B|1I|F|G]|$A|1J|B|1K|F|G]|$A|1L|B|1M|F|G]|$A|1N|B|1O|F|G]]|9|@$A|1P|B|1Q|1|1R]|$A|1S|B|1T|1|1U]|$A|1V|B|1W|1|1X]|$A|1Y|B|1Z|1|20]|$A|21|B|22|1|23]|$A|24|B|25|1|26]]|C|$]]|$1|H|3|-4|5|6|7|27|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|28|8|@$A|29|B|2A|F|G]]|9|@$A|2B|B|2C|1|2D]|$A|2E|B|2F|1|2G]|$A|2H|B|2I|1|2J]]|C|$]]|$1|K|3|-4|5|6|7|2K|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]|S|$5|N|O|P|C|$Q|T]]|U|$5|N|O|P|C|$Q|R]]|V|$5|N|O|P|C|$Q|W]]|X|$5|N|O|P|C|$Q|Y]]|Z|$5|N|O|P|C|$Q|T]]|10|$5|N|O|P|C|$Q|11]]|12|$5|N|O|P|C|$Q|R]]|13|$5|N|O|P|C|$Q|14]]|15|$5|N|O|P|C|$Q|16]]|17|$5|N|O|P|C|$Q|18]]]]

As you have probably seen in the documentation of the Node.js (and Javascript) SDKs, this is not possible, neither with the methods of a <a href="https://firebase.google.com/docs/reference/js/firebase.firestore.DocumentReference" rel="nofollow noreferrer">DocumentReference</a> nor with the one of a <a href="https://firebase.google.com/docs/reference/js/firebase.firestore.CollectionReference" rel="nofollow noreferrer">CollectionReference</a>.
More precisely, the <a href="https://firebase.google.com/docs/reference/js/firebase.firestore.DocumentReference#set" rel="nofollow noreferrer"><code>set()</code></a> and <a href="https://firebase.google.com/docs/reference/js/firebase.firestore.DocumentReference#update" rel="nofollow noreferrer"><code>update()</code></a> methods of a <a href="https://firebase.google.com/docs/reference/js/firebase.firestore.DocumentReference" rel="nofollow noreferrer">DocumentReference</a> both return a Promise containing <code>void</code>, while the <a href="https://firebase.google.com/docs/reference/js/firebase.firestore.CollectionReference" rel="nofollow noreferrer">CollectionReference</a>'s <a href="https://firebase.google.com/docs/reference/js/firebase.firestore.CollectionReference#add" rel="nofollow noreferrer"><code>add()</code></a> method returns a Promise containing a <a href="https://firebase.google.com/docs/reference/js/firebase.firestore.DocumentReference" rel="nofollow noreferrer">DocumentReference</a>.
<hr />
Side Note (in line with answer from darrinm below): It is interesting to note that with the <a href="https://firebase.google.com/docs/firestore/reference/rest" rel="nofollow noreferrer">Firestore REST API</a>, when you <a href="https://firebase.google.com/docs/firestore/reference/rest#rest-resource:-v1.projects.databases.documents" rel="nofollow noreferrer">create a document</a>, you get back (i.e. through the API endpoint response) a <a href="https://firebase.google.com/docs/firestore/reference/rest/v1/projects.databases.documents#Document" rel="nofollow noreferrer"><code>Document</code></a> object.

blocks|key|4029779|text|这似乎是Firestore+Javascript+API的任意限制。Firestore+REST+API在同一次调用中返回更新后的文档。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4029780|https://firebase.google.com/docs/firestore/reference/rest/v1beta1/projects.databases.documents/patch|offset|length|4029781|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2S|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

This appears to be an arbitrary limitation of the the Firestore Javascript API. The Firestore REST API returns the updated document on the same call.

<a href="https://firebase.google.com/docs/firestore/reference/rest/v1beta1/projects.databases.documents/patch" rel="nofollow noreferrer">https://firebase.google.com/docs/firestore/reference/rest/v1beta1/projects.databases.documents/patch</a>

Is it possible to get document back after adding it / updating it without additional network calls with Firestore, similar to MongoDB?

I find it stupid to first make a call to add / update a document and then make an additional call to get it.

Firestore: get document back after adding it / updating it without additional network calls

MongoDB

是否有可能在添加/更新文档后将其取回，而无需使用Firestore进行额外的网络调用，类似于MongoDB？我发现首先调用一个添加/更新文档，然后再调用一个额外的调用来获取它，这是很愚蠢的。

问Firestore:无需额外的网络调用即可在添加/更新文档后将其取回
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Firestore:无需额外的网络调用即可在添加/更新文档后将其取回EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Firestore:无需额外的网络调用即可在添加/更新文档后将其取回
EN