Mongoz allows to take database name at run-time.

[harshalizode]

Hello,
In MongoDB, I have used multiple databases for each organisation, and every database has the same collections like user, employee, branch, etc. In the Mongoz documentation, they have provided the database name in the Meta class; however, this is not a mandatory field.If we can't pass the database name in the meta information, then how can we pass the database name at the query execution using Mongoz?

Thanks.

[tarsil]

@harshalizode isn't the database attribute in the Meta of MongoZ document not being enforced? Of not passed, raises an error? If not, then it's a bug that needs addressing in Mongoz.

In theory, the database attribute should be mandatory.

Thank you for this, of course.

[harshalizode]

Yes, it is mandatory in meta to pass the database name.
Thank you

[tarsil]

Not a problem. How are you finding Esmerald and Mongoz so far? Also, I hope I answered your question 👍🏼

[harshalizode]

Thank you for your quick response.
We have just started development with Esmerald framework, as we are having experience of Django framework, it is easy to understand all the concepts. So far we have found it is good framework for API development.
Regarding Mongoz, we are still exploring on it.

[tarsil]

Oh thank you @harshalizode . The feeling you are having with Esmerald is intentional. I myself came from years of Django and some other frameworks but Django feel was always what pleased me the most. Esmerald was designed to be futuristic for API development and applications with the latest features of python and maintaining the same Django level experience. I'm glad you all are enjoying.

You are all welcome to also contribute if you see fit. Features, bugs, documentation, whatever that you can see that can make it better 👍🏼

[tarsil]

@harshalizode this will be also addressed today and maybe some improvements will be added to Mongoz.

Or we enforce this, or we allow to pass the dB name in the query but most likely we will enforce the database name as it was supposed to.

[harshalizode]

For the time being, I've added the functionality; once the overall flow is complete, I'll test it and make any necessary changes. If everything works as expected, I'll let you know. I really appreciate your prompt reply. It is help me a lot to understand the concepts quickly. Should any obstacles arise, I will get in touch with you once again.

[tarsil]

That is understandable. One way to actually do something like this is having a table where you map a user with the corresponding database and then in the middleware you check the request for the user against that same database and map the query.

This is more multi tenancy design than technology itself and these are just ideas.

[tarsil]

Of course, I will try to help as much as I can and that functionality you did for MongoZ, you can always contribute by adding it in a PR against MongoZ as well.

It is more than welcomed.

[harshalizode]

Thank you.

[harshalizode]

Hello, I am attempting to create an employee document, But it failed to create it because of the abstract property in the Meta class.
The code is below.

 employee = await self.model_class.using(db).create(**kwargs)
 doc_id = employee.id

Document:

{
     'month_period': '202403', 
     'employee_code': '00190', 
     'full_name': 'Emp_Name_190', 
     'date_of_joining': '2011-10-31 00:00:00.000', 
     'e_mail': 'empname190@mail.com', 
     'mobile_no': '3222470621', 
     'domain_login_id': 'Emp_Name_190', 
     'line_of_business': 'Branch', 
     'last_modified_date': '2024-03-28 17:53:51.163'
}

Model:

class Employee(Document):

    month_period: str = mongoz.Integer
    full_name: str = mongoz.String
    employee_code: str = mongoz.String
    date_of_joining: str = mongoz.DateTime
    e_mail: str = mongoz.String
    mobile_no: str = mongoz.String
    domain_login_id: str = mongoz.String
    line_of_business: str = mongoz.String
    last_modified_date: str = mongoz.DateTime

    objects: ClassVar[CustomManger] = CustomManger()

    class Meta:
        abstract = False
        registry = registry
        database = default_db_name

Its raises:

raise AbstractDocumentError(
mongoz.exceptions.AbstractDocumentError: Employee(id=None) is an abstract class. This operation is not allowed

The problem is that it treats the abstract property default as True.
I set the abstract argument to False in the Meta class, and it still raises the same exception.

[harshalizode]

Hi, what database? Mongoz? Why don't you have a look at the documentation?
I am trying to implement changes in the registry and query manager using the "using" method, so I need a guidance to implement changes to make a connection with the mongoDB with the different databases at the run time .
I'm struggling to understand the question, apologies for that.

https://mongoz.tarsild.io and this would probably help you since you can also see the source code 🙂

If you are referring to Mongoz, then the connection is stored inside the Registry:

https://github.com/tarsil/mongoz/blob/main/mongoz/core/connection/registry.py

[tarsil]

Apologies for my confusion. I understood after. MongoZ uses Motor to manage the connections inside the Registry.

Mongoz follows the same patterns of Saffier and Edgy. More for consistency.

[harshalizode]

Thank you for providing the clarification regarding MongoZ and Motor, and I now understand how Motor manages the connections within the registry.

[tarsil]

No problem @harshalizode 🙂

[harshalizode]

Thank you for your response, waiting for the version 0.8.0. :D