Add "using" method in model queryset manager, which will be used to change database at runtime while querying.

[harshalizode]

The "using" method allows us to change the database at runtime while querying. If the user does not use the "using" method, it behaviour the same as before; however, I have included logic to change the database during runtime.

It is compatible with create, get, all, filter, with the exception of the update query, which needs to be modified in order to be used with the "using" method because it creates duplicate documents with the updated one.

We can use the "using" method as follows:

User.objects.using("DB_NAME").all()

[tarsil]

@harshalizode this is great! Thank you so much for this but I need to ask you a couple of things.

Can you update the docs to also have this using referenced there, please? Maybe in the queries.md?

Also, some tests to this would be great to have. Since it's mongo db, you can pass in the meta whatever you need.

Having all of this, we can release it today

[harshalizode]

I have updated the doc and wrote test cases for it, and it passed.

[tarsil]

@harshalizode the linting is failing.

In your local machine run:

scripts/lint

This should fix the problems

[harshalizode]

Which linter is used in MongoZ?

[tarsil]

@harshalizode mongoz repo has everything you need. Here https://mongoz.tarsild.io/contributing/ contains what you need to do to run it locally.

Although there is a bug there I need to fix. its not scripts/format anymore but scripts/lint.

When you install the requirements and run those commands and pass, it should pass in the CI as well since it uses the same.

We use in the script ruff black and mypy. That is why its easier to run it after installing the requirements.

[tarsil]

@harshalizode if you can run the scripts/install + scripts/lint this errors should be easily addressed and you can push them.

It would be great to have this great feature in Mongoz.

[harshalizode]

I have resolved the Linter issues.

[tarsil]

@harshalizode still complains? Did you run the scripts/lint?

Maybe you can also install the pre-commits and run it

[harshalizode]

I have resolved all the issues.

[tarsil]

I have resolved all the issues.

I can see that but once you resolve them you need to still do a git add and git push for the CI to run.

You can see the error https://github.com/tarsil/mongoz/actions/runs/8875747891/job/24365837286?pr=28

[tarsil]

Maybe here it is better to

 collection: Union[AsyncIOMotorCollection, None] = None

[harshalizode]

Done.

[tarsil]

Overall the PR looks good besides the minor changes requested 👍🏼

[tarsil]

@harshalizode the linting is still a problem.

This is what I would do.

1. Install the pre-commit
2. git init (no worries just to start the pre commit)
3. scripts/lint
4. git add
5. git push

[harshalizode]

Yes, after following the steps, I had two issues, which I resolved.

[tarsil]

@harshalizode congratulation! Your PR made it into the new release 0.8.0 :)

Thank you so much, I hope Mongoz and Esmerald are treating you well.

[harshalizode]

Thanks for all your assistance :)

[tarsil]

Thanks for all your assistance :)

Anytime :). How is Esmerald and Mongoz working for you?

[harshalizode]

Both Esmerald and Mongoz are nice, but when utilizing Esmerald with Mongoz, there are certain difficulties, such as:

1. Extending a Document to override the QueryManager.
2. MOGOZ.Date field has a parsing issue.
   We have identified a few problems and need to find a solution.

[tarsil]

@harshalizode ok good to know. Let's fix those then. Esmerald has nothing to do with that apparently. Do you still have the extending problem?

Can you provide me examples of all the issues you are currently facing?

This way we can address them

[harshalizode]

Yes, there is still an issue with overriding the QueryManager.

I use the Abstract document as the BaseDocument by inheriting the mongoz.Document.
I have replaced the Quermanager with the CustomManager.

class BaseDocument(mongoz.Document):
    """
    The base document for all documents using the `registry` registry.
    """
    objects: ClassVar[CustomManger] = CustomManger()

    class Meta:
        """
            It contains the Meta information related the database for \
                each model level.
        """
        abstract = True
        registry = settings.client
        database = settings.db

Now, I'm trying to inherit the BaseDocument into my view as

class Employee(BaseDocument):
    month_period: int = mongoz.Integer(null=True)
    full_name: str = mongoz.String()
    employee_code: str = mongoz.String()
    date_of_joining: datetime.datetime = mongoz.DateTime(null=True)
    e_mail: str = mongoz.String(null=True)
    mobile_no: str = mongoz.String(null=True)

Whenever I try to query in MongoDB using the manager as Employee.objects.all()
Employee.objects returns me the Manager (Default Manager) and not the CustomManager.

That's why I'm overriding the manager at the model level.

class Employee(BaseDocument):
    month_period: int = mongoz.Integer(null=True)
    full_name: str = mongoz.String()
    employee_code: str = mongoz.String()
    date_of_joining: datetime.datetime = mongoz.DateTime(null=True)
    e_mail: str = mongoz.String(null=True)
    mobile_no: str = mongoz.String(null=True)

    objects: ClassVar[CustomManger] = CustomManger()

Thanks.