mgo.v2 Find().Select().One()返回空白



mongo shell输出

> db.departments.find()
{ "_id" : ObjectId("5733b051e444917f9d273ce6"), "id" : "5733b05157659a11a4589102", "brandid" : "1", "name" : "first", "managerid" : "0", "users" : [ "1", "2", "3", "7" ] }

该函数将depID作为输入,我验证了它应该是什么,即5733b05157659a11a4589102

func GetUsers(depID string) (*department.UsersResp, error) {
    if !bson.IsObjectIdHex(depID) {
        return nil, fmt.Errorf("%s is not a ObjectId value", depID)
    }
    type UserResp struct {
        users []string 
    }
    var result *UserResp
    err := coll.Find(bson.M{"id": depID}).Select(bson.M{"users": 1}).One(&result)
    if err != nil {
    fmt.Println(err, result)
        return nil, err
    }
    fmt.Println("result:",result)
    //ignore return type and value the above print is what i have doubt about
    return result, nil
}

结果输出为{[]}

除了上面的查询,我还尝试了以下查询
err := coll.Find(bson.M{"id": depID})One(&result)
err := coll.Find(nil).One(&result)
结果是一样的。

数据库连接和其他一切都很好,因为使用相同变量coll的同一文件的所有其他函数都可以使用

更多信息我也试过这个

type UserResp struct {
   users []string `json:"users" bson:"users"`
}

Mongo LOG

MGO: cluster.go:590: Cluster has 1 known masters and 0 known slaves.
MGO: socket.go:391: Socket 0xc8201340e0 to 127.0.0.1:27017: serializing op: &mgo.queryOp{collection:"departments.departments", query:bson.M{"id":"5733b05157659a11a4589102"}, skip:0, limit:-1, selector:bson.M{"users":1}, flags:0x4, replyFunc:(mgo.replyFunc)(0x58eef0), mode:1, options:mgo.queryWrapper{Query:interface {}(nil), OrderBy:interface {}(nil), Hint:interface {}(nil), Explain:false, Snapshot:false, ReadPreference:bson.D(nil), MaxScan:0, MaxTimeMS:0, Comment:""}, hasOptions:false, serverTags:[]bson.D(nil)}
MGO: socket.go:521: Socket 0xc8201340e0 to 127.0.0.1:27017: sending 1 op(s) (106 bytes)
MGO: socket.go:311: Socket 0xc8201340e0 to 127.0.0.1:27017: updated write deadline to 1m0s ahead (2016-05-12 10:18:17.811427695 -0400 EDT)
MGO: socket.go:311: Socket 0xc8201340e0 to 127.0.0.1:27017: updated read deadline to 1m0s ahead (2016-05-12 10:18:17.811468447 -0400 EDT)
MGO: socket.go:563: Socket 0xc8201340e0 to 127.0.0.1:27017: got reply (106 bytes)
MGO: socket.go:622: Socket 0xc8201340e0 to 127.0.0.1:27017: received document: bson.M{"_id":"W3xb0Qxe4Dx91u007fx9d'<xe6", "users":[]interface {}{"1", "2", "3", "7"}}
MGO: session.go:3062: Query 0xc82012c000 document unmarshaled: &db.UserResp{users:[]string(nil)}
{[]}

我认为问题可能是您的UserResp结构具有私有成员。

//Instead of
 users []string `json:"users" bson:"users"`
// Try
 Users []string `json:"users" bson:"users"`

一个疯狂的猜测,但也许可以尝试

var result UserResp

而不是使用指针。

正如Walt所提到的,您还应该导出Users字段。

  1. users未导出,应为Users
  2. 你不需要一个指向指针的指针,我个人只需要使用var result UserResp

以下更正:

type UserResp struct {
    Users []string 
}
var result UserResp
err := coll.Find(bson.M{"id": depID}).Select(bson.M{"users": 1}).One(&result)

如果不是这些问题,我在处理BSON和数组/切片时遇到了很多问题。您可以尝试将Users作为接口的一部分,或者将整个输出写入bson。M映射(map[string]interface{}),然后从那里开始。我会这样做:

var result bson.M
err := coll.Find(bson.M{"id": depID}).Select(bson.M{"users": 1}).One(&result)

您可以使用类型断言访问底层数据:

result["users"].([]string)

如果这不起作用,只需检查底层数据以调试返回的类型:

fmt.Printf("%+v", result)

不管怎样,一旦你在Go中有了这样的数据。它将更容易调试。

最新更新