Go语言如何在单个函数中解码不同文件的两个结构体？

Hey there! Let's tackle this struct decoding issue you're having when saving data to your MongoDB collection. First, let's break down common pitfalls using the User struct you shared, then cover considerations for your second struct too.

1. Mismatched or Missing BSON Tags (Top Culprit) #

Looking at your User struct:

type User struct { 
    Id int `json:"id" bson:"_id,omitempty"` 
    FirstName string `json:"first_name,omitempty" bson:"first_name,omitempty"` 
    LastName string `json:"last_name,omitempty" bson:"last_name,omitempty"` 
    EmailId string `json:"email_id,omitempty" bson:"email_id,omitempty"` 
    Password string `json:"password,omitempty"` 
}

• The Password field has a JSON tag but no BSON tag. The MongoDB Go driver relies on BSON tags to map struct fields to database keys. Without it, the driver won't know how to save or load this field. Fix it by adding the BSON tag:

  Password string `json:"password,omitempty" bson:"password,omitempty"`
  

• Also, MongoDB's default _id type is ObjectId (not int), unless you explicitly configure integer IDs. If you want MongoDB to auto-generate the ID, switch the Id type to primitive.ObjectID (from the go.mongodb.org/mongo-driver/bson/primitive package):

  Id primitive.ObjectID `json:"id,omitempty" bson:"_id,omitempty"`
  

  If you need to use integer IDs, make sure you manually set the Id value before saving, and your collection is set up to handle integer _id values.

2. Issues with Your Second Struct #

Since you mentioned two different structs, apply these checks to the other one too:

• Ensure every field you want to persist has a correct BSON tag (matching database keys for reading, or defining keys for writing).
• Double-check that required fields (like EmailId if it's mandatory) aren't marked with omitempty if you need them to always be present in the database.

3. Driver or Context Setup Mistakes #

• When using the MongoDB Go driver, use the official decoding methods instead of manual unmarshalling. For example:

  err := collection.FindOne(ctx, bson.M{"email_id": "user@example.com"}).Decode(&user)
  if err != nil {
      // Handle error here
  }
  

• Verify your client is properly connected to the database, and you're targeting the correct collection name (typos here often lead to silent failures or decoding errors).

4. Type Mismatches Between Struct and Database Data #

• If you're decoding existing data from MongoDB, make sure the data types match exactly. For example, if the database stores _id as an ObjectId but your struct uses int, decoding will fail immediately.
• Check that string fields in your struct don't correspond to numeric values in the database (and vice versa).

Quick Debugging Hack #

Always print the exact error message you're getting! The MongoDB driver provides descriptive errors that point directly to the problem. For example:

err := collection.InsertOne(ctx, &user)
if err != nil {
    fmt.Printf("Save error: %v\n", err)
}

This will tell you if it's a tag issue, type mismatch, or something else entirely.

内容的提问来源于stack exchange，提问作者Puneet