2012-08-13 24 views
0

我已经尝试了两种不同的方式来使用Doctrine的MongoDB-ODM进行相同的查询。为什么doctrine2 ODM的findBy()和createQueryBuilder() - > getQuery() - > execute()的结果各不相同?

你能弄清楚为什么这两个,在我看来类似的查询都返回不同的结果?代码片段1不会返回片段2返回正确数据库条目的任何内容。这两个查询在日志文件中看起来很相似 - 除了#1没有跳过限制行&。对于片段2

[2012-08-13 09:14:33] doctrine.INFO: MongoDB query: { "find": true, "query": { "targetUser": ObjectId("4fa377e06803fa7303000002"), "code": { "$in": [ "login.attempt", "login.ok" ] }, "ts": [ "$gte", new Date("Sun, 12 Aug 2012 09:14:33 +0000") ] }, "fields": [ ], "db": "eventio_com", "collection": "ActivityEvent" } [] [] 
[2012-08-13 09:14:33] doctrine.INFO: MongoDB query: { "sort": true, "sortFields": { "ts": 1 }, "query": { "targetUser": ObjectId("4fa377e06803fa7303000002"), "code": { "$in": [ "login.attempt", "login.ok" ] }, "ts": [ "$gte", new Date("Sun, 12 Aug 2012 09:14:33 +0000") ] }, "fields": [ ] } [] [] 

片段2

$recentLoginsQuery = $this->get('user_activity_tracker')->createQueryBuilder() 
     ->field('targetUser')->equals($userAccount->getId()) 
     ->field('code')->in(array('login.attempt','login.ok')) 
     ->field('ts')->gte($dateDayAgo) 
     ->sort('ts','asc') 
     ->getQuery(); 

$recentLogins = $recentLoginsQuery->execute(); 

日志条目:

片段1

$dateDayAgo = new \DateTime('1 day ago'); 
$recentLogins = $this->get('user_activity_tracker')->findBy(array(
     'targetUser' => $userAccount->getId(), 
     'code' => array('$in' => array('login.attempt','login.ok')), 
     'ts' => array('$gte', $dateDayAgo) 
    ))->sort(['ts' => 1]); 

Symfony的日志从片段1项

[2012-08-13 09:17:30] doctrine.INFO: MongoDB query: { "find": true, "query": { "targetUser": ObjectId("4fa377e06803fa7303000002"), "code": { "$in": [ "login.attempt", "login.ok" ] }, "ts": { "$gte": new Date("Sun, 12 Aug 2012 09:17:30 +0000") } }, "fields": [ ], "db": "eventio_com", "collection": "ActivityEvent" } [] [] 
[2012-08-13 09:17:30] doctrine.INFO: MongoDB query: { "limit": true, "limitNum": null, "query": { "targetUser": ObjectId("4fa377e06803fa7303000002"), "code": { "$in": [ "login.attempt", "login.ok" ] }, "ts": { "$gte": new Date("Sun, 12 Aug 2012 09:17:30 +0000") } }, "fields": [ ] } [] [] 
[2012-08-13 09:17:30] doctrine.INFO: MongoDB query: { "skip": true, "skipNum": null, "query": { "targetUser": ObjectId("4fa377e06803fa7303000002"), "code": { "$in": [ "login.attempt", "login.ok" ] }, "ts": { "$gte": new Date("Sun, 12 Aug 2012 09:17:30 +0000") } }, "fields": [ ] } [] [] 
[2012-08-13 09:17:30] doctrine.INFO: MongoDB query: { "sort": true, "sortFields": { "ts": 1 }, "query": { "targetUser": ObjectId("4fa377e06803fa7303000002"), "code": { "$in": [ "login.attempt", "login.ok" ] }, "ts": { "$gte": new Date("Sun, 12 Aug 2012 09:17:30 +0000") } }, "fields": [ ] } [] [] 

我的'user_activity_tracker'服务只是作为底层Doctrine存储库/文档管理器的代理。这两个片段在查询后都会返回一个LoggableCursor。

回答

0

使用查询生成器方法的额外日志输出是由于Query::prepareCursor(),它始终设置其他游标选项。如果提供非空值,则使用DocumentPersister::loadAll()的存储库findBy()方法仅设置选项。这解释了日志输出的差异,但与结果集的差异无关。

除了ts条件的小漂移之外,每个示例的记录查询都是相同的。如果两个游标的count()值不同,并且在将光标解包为iterator_to_array()后结果不同,我会建议尝试在失败的测试用例中重现此操作,并提交针对mongodb-odm存储库的拉取请求。

+0

再次感谢您,我会再回到这个问题上。 – 2012-08-13 19:15:36

相关问题