如何在使用Jackson反序列化OffsetDateTime时保留偏移量(How to preserve the offset while deserializing OffsetDateTime with Jackson)

 欢迎来到SO！ 
 
 你似乎在Pub / Sub和Collection.find之间感到困惑。 
 
 你应该首先意识到2是不同的机制，它们提供不同的功能。 
 
 
 
 Pub / Sub的确将数据从服务器发送到客户端的Minimongo数据库。 但是这些数据还没有显示出来。 
 
 
 Collection.find在您的服务器上针对您的实际MongoDB使用，在您的客户端针对您当地的Minimongo DB使用。 
 
 
 因此，在您的客户端上，一旦您正确订阅了您的服务器发布（通常在应用程序级别或模板级别/ onCreated钩子中），您可以直接在助手（或任何其他地方）中调用Jobs.find来获取文档，改变订阅（除非后者需要新的参数）。 
 
 你的评论代码应该没有问题： 
 
return Job.find({'_id': { '$in': companyJobs }});
 
 一般来说，避免在助手（如Meteor.subscribe ）中进行任何昂贵的计算，因为助手可能会执行很多次而不会注意到它。 你的Meteor.subscribe('Companies')也应该进入模板级别（即在onCreated钩子）。 
 
 因此，不要在助手中执行if / else条件，只需在模板级别执行一次即可。 为了说明您需要使用另一个集合中其他文档的值，为什么不直接将公司的slug作为参数传递给您的Jobs订阅，并执行计算Server端？ 或者甚至只是订阅一切，因为您目前的初始订阅似乎是这样做的。 
 
 然后，您的帮手将只使用Jobs.find ，这会查询您客户的本地minimongo数据库，从而让您的服务器不受干扰。 

Welcome to SO!
 
You seem to be confused between Pub/Sub and Collection.find.
 
You should first realize that the 2 are different mechanisms, which provide different functionalities.
 
 
 
Pub/Sub indeed sends data from your Server into your Client's Minimongo database. But this data is not displayed yet.
 
 
Collection.find is used on your Server against your actual MongoDB, and on your Client against your local Minimongo DB.
 
 
Therefore on your client, once you have correctly subscribed to your server publication (typically at app level or template level / in onCreated hook), you can directly call Jobs.find in your helpers (or anywhere else) to get your documents, without having to change the subscription (unless the latter needs new parameters).
 
There should be nothing wrong with your commented code:
 
return Job.find({'_id': { '$in': companyJobs }});
 
In general, avoid any expensive computation in helpers (like Meteor.subscribe), as helpers may be executed many times without you noticing it. Your Meteor.subscribe('Companies') should also go to template level (i.e. in onCreated hook).
 
Therefore, instead of doing your if / else conditions in your helper, simply do it once at your template level. To account for your need to use a value from another document in another collection, why not just passing directly the company's slug as an argument to your Jobs subscription, and performing the computation Server-side? Or even just subscribing to everything, as your current initial subscription seems to do.
 
Then your helper will just use Jobs.find, which queries against your Client's local minimongo DB, leaving your Server unbothered.