FastAPI中MongoDB数组位置操作符失效问题排查

1. MongoDB文档结构 #

{
  "_id": "cc3a8d7f-5962-47e9-a3eb-09b0a57c9fdb",
  "isDeleted": false,
  "user": {
    "timestamp": "2023-02-12",
    "name": "john",
    "surname": "doe",
    "email": "a.s@ug.bilkent.edu.tr",
    "phone": "+012345678912",
    "age": 25,
    "gender": "female",
    "nationality": "smth",
    "universityMajor": "ENGINEERING",
    "preferences": null,
    "highPrivacy": false
  },
  "postings": [
    {
      "id": "f61b103d-8118-4054-8b24-b26e2f4febc4",
      "isDeleted": false,
      "timestamp": "2023-02-12",
      "houseType": "apartment",
      "totalNumOfRoommates": 5,
      "location": {
        "neighborhood": "Oran",
        "district": "Çankaya",
        "city": "Adana"
      },
      "startDate": "2022-11-10",
      "endDate": "2022-11-15",
      "postingType": "House Sharer",
      "title": "House sharer post 1",
      "description": "This is house sharer post 1",
      "price": 2500,
      "houseSize": "2 + 0"
    },
    {
      "id": "b7d34113-1b13-4265-ba9b-766accecd267",
      "isDeleted": false,
      "timestamp": "2023-02-12",
      "houseType": "apartment",
      "totalNumOfRoommates": 5,
      "location": {
        "neighborhood": "Dikmen",
        "district": "Çankaya",
        "city": "Adana"
      },
      "startDate": "2022-09-13",
      "endDate": "2023-12-24",
      "postingType": "House Seeker",
      "startPrice": 2002,
      "endPrice": 2500
    }
  ]
}

2. 最初的实现代码（存在问题） #

尝试通过FastAPI接口将指定ID的posting标记为已删除，但代码存在逻辑错误：

@router.delete('/{id}', response_description='Deletes a single posting')
async def deletePost(id: str):       

    update_result = await dbConnection.update_one(
        {"postings.id": id, "postings.isDeleted" : False}, 
        {"$set" : {"postings.$.isDeleted" : True} }
    )
    if update_result.modified_count == 1:
        return Response(status_code=status.HTTP_204_NO_CONTENT)
    else:
        raise HTTPException(status_code=404, detail=f"Post {id} not found or has already been deleted")

3. 遇到的问题 #

调用接口传入指定posting ID（如b7d34113-1b13-4265-ba9b-766accecd267）时，被标记为已删除的总是数组中的第一个文档；再次调用接口，会按数组顺序依次标记后续元素，完全忽略传入的目标ID。

4. 问题原因 #

MongoDB的位置操作符$在查询条件包含多个数组字段条件时，只会匹配第一个满足任意单个条件的数组元素，而非同时满足所有条件的元素。原查询条件{"postings.id": id, "postings.isDeleted" : False}的逻辑是：检查数组中是否存在ID匹配的元素，且数组中是否存在isDeleted为False的元素，而不是定位到同时满足ID匹配且isDeleted为False的单个元素，因此$会默认指向数组的第一个元素。

5. 正确的实现代码 #

使用MongoDB的**数组过滤器（array_filters）**可以精准定位目标数组元素，修正后的代码如下：

update_result = await dbConnection.update_one(
        {"postings.id": id},
        {
            "$set": {
                "postings.$[p].isDeleted": True
            }
        },
        array_filters=[
            {
                "p.id": id,
                "p.isDeleted": False
            }
        ]
    )

6. 代码说明 #

• 通过$[p]占位符指定要更新的数组元素位置
• array_filters中的条件{"p.id": id, "p.isDeleted": False}确保只匹配同时满足ID一致且未被删除的posting元素
• 无需设置upsert=True，因为我们只是更新已存在的文档，不需要插入新文档

内容的提问来源于stack exchange，提问作者Ahmet-Salman