MongoEngine / MongoEngine/mongoengine

Calling .only() on a field that has not been set does not go to default value

Open
#2,398 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
4.3k
Forks
1.2k
Avg merge
4h 41m
Merged PRs (30d)
11

Description

I've had this issue a few times now, where I'm calling .only() for efficiency, and then when using the value, I don't get the default, I get None returned.

Other fields not specified in the .only() function do get set to their default value, however.

Reproduce:


class Example(Document):
    meta = {"collection": "example"}

    str1 = StringField(default="hi")
    str2 = StringField(default="hi2")

Example().save()
a = Example.objects.only("str1").first() # a.str1 == None, a.str2 == "hi2"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the provided Example document and the Example.objects.only("str1").first() reproduction, then trace how .only() loads unspecified fields and applies defaults. Done means the reproduced str1 access returns "hi" while the projection behavior remains intact, with a regression test covering the example.

Written by the indexing model from the issue text.

Assessment

Tech stack
mongodb, python
Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.