A Python Object-Document-Mapper for working with MongoDB

Overview

MongoEngine

Info: MongoEngine is an ORM-like layer on top of PyMongo.
Repository: https://github.com/MongoEngine/mongoengine
Author: Harry Marr (http://github.com/hmarr)
Maintainer: Stefan Wójcik (http://github.com/wojcikstefan)
https://travis-ci.org/MongoEngine/mongoengine.svg?branch=master https://coveralls.io/repos/github/MongoEngine/mongoengine/badge.svg?branch=master

About

MongoEngine is a Python Object-Document Mapper for working with MongoDB. Documentation is available at https://mongoengine-odm.readthedocs.io - there is currently a tutorial, a user guide, and an API reference.

Supported MongoDB Versions

MongoEngine is currently tested against MongoDB v3.4, v3.6 and v4.0. Future versions should be supported as well, but aren't actively tested at the moment. Make sure to open an issue or submit a pull request if you experience any problems with MongoDB version > 4.0.

Installation

We recommend the use of virtualenv and of pip. You can then use python -m pip install -U mongoengine. You may also have setuptools and thus you can use easy_install -U mongoengine. Another option is pipenv. You can then use pipenv install mongoengine to both create the virtual environment and install the package. Otherwise, you can download the source from GitHub and run python setup.py install.

The support for Python2 was dropped with MongoEngine 0.20.0

Dependencies

All of the dependencies can easily be installed via python -m pip. At the very least, you'll need these two packages to use MongoEngine:

  • pymongo>=3.4

If you utilize a DateTimeField, you might also use a more flexible date parser:

  • dateutil>=2.1.0

If you need to use an ImageField or ImageGridFsProxy:

  • Pillow>=2.0.0

If you need to use signals:

  • blinker>=1.3

Examples

Some simple examples of what MongoEngine code looks like:

from mongoengine import *
connect('mydb')

class BlogPost(Document):
    title = StringField(required=True, max_length=200)
    posted = DateTimeField(default=datetime.datetime.utcnow)
    tags = ListField(StringField(max_length=50))
    meta = {'allow_inheritance': True}

class TextPost(BlogPost):
    content = StringField(required=True)

class LinkPost(BlogPost):
    url = StringField(required=True)

# Create a text-based post
>>> post1 = TextPost(title='Using MongoEngine', content='See the tutorial')
>>> post1.tags = ['mongodb', 'mongoengine']
>>> post1.save()

# Create a link-based post
>>> post2 = LinkPost(title='MongoEngine Docs', url='hmarr.com/mongoengine')
>>> post2.tags = ['mongoengine', 'documentation']
>>> post2.save()

# Iterate over all posts using the BlogPost superclass
>>> for post in BlogPost.objects:
...     print('===', post.title, '===')
...     if isinstance(post, TextPost):
...         print(post.content)
...     elif isinstance(post, LinkPost):
...         print('Link:', post.url)
...

# Count all blog posts and its subtypes
>>> BlogPost.objects.count()
2
>>> TextPost.objects.count()
1
>>> LinkPost.objects.count()
1

# Count tagged posts
>>> BlogPost.objects(tags='mongoengine').count()
2
>>> BlogPost.objects(tags='mongodb').count()
1

Tests

To run the test suite, ensure you are running a local instance of MongoDB on the standard port and have pytest installed. Then, run python setup.py test or simply pytest.

To run the test suite on every supported Python and PyMongo version, you can use tox. You'll need to make sure you have each supported Python version installed in your environment and then:

# Install tox
$ python -m pip install tox
# Run the test suites
$ tox

If you wish to run a subset of tests, use the pytest convention:

# Run all the tests in a particular test file
$ pytest tests/fields/test_fields.py
# Run only particular test class in that file
$ pytest tests/fields/test_fields.py::TestField

Community

Contributing

We welcome contributions! See the Contribution guidelines

Comments
  • Pymongo3 compatibility

    Pymongo3 compatibility

    Hi guys,

    Now everything is fixed and is fully compatible for both PyMongo 2.X and 3.X

    I'm awaiting some feedback for:

    1. ~~The way I introduced differential behaviour based on PyMongo version~~
    2. ~~The behaviour for save() when a document is created with a given primary key, source of 5 of remaining issues. Here particularly, I have removed the check for self._created since we used to modify this why changing/switching db on the fly. This whole behaviour has changed in PyMongo3 and IMHO doesn't make sense anymore.~~
    3. ~~Your opinion if the test_hint failure could point to a bug in PyMongo3~~
    4. ~~A hand on the other error on test_geo_indexes_recursion~~
    5. ~~A problem with binary field used as primary index that was always there and only discovered now by a better test that became mandatory by the use of a work-around concerning a PyMongo 3.0 bug already fixed in the upcoming 3.0.1~~

    Cheers, Matthieu

    Review on Reviewable

    opened by MRigal 113
  • Tox support for cross-versions testing

    Tox support for cross-versions testing

    Mongoengine is tested on different PyMongo versions, different Python versions... This pull-request add a tox.ini file allowing to run the test suite on every supported version composition . This allow to do proper testing before submitting pull-requests without having to wait for TravisCI cross-versions testing.

    To run the test in tox, simply run:

    $ tox
    

    It will create a virtualenv for each combination and run the same test suite (like TravisCI).

    Review on Reviewable

    opened by noirbizarre 78
  • Fixes #934 - Added option to disable field existence check.

    Fixes #934 - Added option to disable field existence check.

    I threw together this patch as an idea to fix #934.

    I haven't dug too deep into Mongoengine to know what else this might affect, but I used _from_son in BaseDocument object as my injection point. The idea being that if one tries to define in code a field that does not exist, an error is still raised, but if one pulls in data from a PyMongo object, we don't raise an error.

    Review on Reviewable

    opened by gordol 64
  • mark_as_changed issue

    mark_as_changed issue

    fix mark_as_changed: rm lower level changed fields otherwise may cause conflict update error this issue appears when retrieve from db

    In [34]: class Foo(mongoengine.Document):
    
        bar = mongoengine.DictField()
       ....:     
    
    In [35]: Foo.objects.delete()
    Out[35]: 1
    
    In [36]: foo = Foo()
    
    In [37]: foo.save()
    Out[37]: <Foo: Foo object>
    
    In [38]: foo = Foo.objects.first()
    
    In [39]: foo.bar['what'] = 'ever'
    
    In [40]: foo.bar['other'] = {}
    
    In [41]: foo._changed_fields
    Out[41]: ['bar.what', 'bar.other']
    
    In [42]: foo.bar['other']['what'] = 'ever'
    
    In [43]: foo._changed_fields
    Out[43]: ['bar.what', 'bar.other', 'bar.other.what']
    
    In [44]: foo.save()
    ---------------------------------------------------------------------------
    OperationError                            Traceback (most recent call last)
    <ipython-input-44-e6645f54a3c0> in <module>()
    ----> 1 foo.save()
    
    .../mongoengine/document.pyc in save(self, force_insert, validate, clean, write_concern, cascade, cascade_kwargs, _refs, save_condition, **kwargs)
        365                 message = u'Tried to save duplicate unique keys (%s)'
        366                 raise NotUniqueError(message % unicode(err))
    --> 367             raise OperationError(message % unicode(err))
        368         id_field = self._meta['id_field']
        369         if created or id_field not in self._meta.get('shard_key', []):
    
    OperationError: Could not save document (Cannot update 'bar.other' and 'bar.other.what' at the same time)
    

    Review on Reviewable

    opened by Catstyle 53
  • _get_changed_fields fix for embedded documents with id field.

    _get_changed_fields fix for embedded documents with id field.

    When id field presented in Embedded document, changes inside this document was ignored in method _get_changed_fields because it's id was added to inspected array before processing it fields. Also modify unittests for _delta method, which fails without code modification.

    Review on Reviewable

    opened by elephanter 45
  • Cannot connect to database default : False is not a read preference.

    Cannot connect to database default : False is not a read preference.

    I use connect(host='mongodb://username:password@localhost:port/database') in my django settings.py. Run server then got a report:

    mongoengine.connection.ConnectionError: Cannot connect to database default :
    False is not a read preference.
    

    Is this a bug or not? Write in python 3.4.3 with django 1.8 and mongoengine 0.9.0

    Awaiting Response Client/Connect 
    opened by GroverChouT 38
  • Delete returns None but expected a dict

    Delete returns None but expected a dict

    I'm trying to delete a document with self.delete() but it raises and error: File "/Users/garito/TimeFounder/App/0.3/env/lib/python2.7/site-packages/mongoengine/queryset/base.py", line 467, in delete return result["n"] TypeError: 'NoneType' object has no attribute 'getitem'

    I've checked the result with print result and it is None The deletion is made ok but the try to return result["n"] raises and error because result is None

    Did I missed something or did I find a bug?

    Thanks!

    Bug 
    opened by Garito 28
  • Check if undefined fields are supplied on document

    Check if undefined fields are supplied on document

    If an undefined field is supplied to a document instance, a FieldDoesNotExist Exception will be raised. This way, you will be notified when you provide a field that does not exist.

    ATM when you do this:

    MyDoc(undefined_field="test")
    

    It will create a document instance for MyDoc. However, if undefined_field does not exist, the value test won't end up anywhere. You'll think the object is successfully created with the provided values, but actually it isn't.

    To remedy this situation, an exception will be raised. This way you'll be noticed about your mistake in development. If the document instance is created dynamically on bases of an API call data for example, then you can catch the exeption and notify the API user that they have provided an undefined field.

    opened by gitaarik 28
  • save doesn't work for datetime consistent with other fields.

    save doesn't work for datetime consistent with other fields.

    I am new to mongoengine, but this doesn't make any sense to me, that when I call my my_update() function, the user's updated_at field doesnt get updated but other fields do. here is my model:

    class User(db.Document):
        username = db.StringField(required=True, unique=True, max_length=20)
        created_at = db.DateTimeField(default=datetime.datetime.utcnow())
        updated_at = db.DateTimeField()
        friend_list = ListField(StringField(max_length=100))
    

    when I do a save, it saves the new friend_list correctly but it keeps the old updated_at field, and that one will never get updated again.

    def my_update(user_id):
        form = UserForm()
        user = User.objects.get_or_404(id=user_id)
        user.friend_list = insert_random_data()
        user.updated_at = datetime.datetime.utcnow()
        user.save()
        return users = User.objects.order_by('-updated_at', '-created_at')
    

    so if I run my_update a few times, it will update the friend_list each time, but the update_at field keeps staying the same !!! and I have no idea. I am really curious why is it behaving like this !

    opened by medyagh 27
  • Pep8 and more clean-up

    Pep8 and more clean-up

    Hi guys,

    Several times I ran into some cases where I came across these init() method returning a value, or some unused statements or variables, as well as many pep8 issues. It is never great to make a big change, but since we are now cleaning so many PRs and there will be anyway a big PR with #946 for next version, I thought it could be a good time to clean generally some code.

    I took some time to really read once (quickly) all the code line by line. It allowed me also to find some issues or strange behaviour and to add some TODOs.

    I would also like to take the opportunity to tackle one other point. We want to be PEP8 conform and this is very good. However one point is at least vague: line length. We have in our code some pieces which are strictly limited to 79 characters and some others to 119.

    PEP8 recommends 79 characters, however Django makes some exceptions there: https://docs.djangoproject.com/en/1.8/internals/contributing/writing-code/coding-style/

    Should we include the same point in our contribution guidelines? Some PRs have a lot of code doing only line breaks clean-up (which I tried to avoid in this cleaning effort to avoid unnecessary changes). And at the same time, I see a lot of places in the code where we have line breaks that do make the code significantly harder to read. @rozza @DavidBord @thedrow @seglberg @yograterol can I have your opinion on that point?

    Review on Reviewable

    opened by MRigal 27
  • fixed wrong _delta results on nested MapFields #931

    fixed wrong _delta results on nested MapFields #931

    Fix for #931 issue. When model restored from database and there is a nested MapField there is an error in wrong key for changes when trying to add/change item in lower-level MapField.

    Review on Reviewable

    opened by elephanter 24
  • Query MapField by a key that matches one of the field names in the nested document fails with a mongoengine.errors.InvalidQueryError

    Query MapField by a key that matches one of the field names in the nested document fails with a mongoengine.errors.InvalidQueryError

    Here is the class hierarchy:

    class DataItem(EmbeddedDocument):
        key = StringField(required=True)
        value = StringField(required=True)
    
    class MyDoc(Document):
        data = MapField(
            field=EmbeddedDocumentField(DataItem)
        )
        
    

    And the data in db:

    {
        "_id" : ObjectId("63a87cb374d6bc3efd9ea570"),
        "data" : {
            "key" : {
                "key" : "1",
                "value" : "test"
            }
        }
    }
    {
        "_id" : ObjectId("63a87cb374d6bc3efd9ea571"),
        "data" : {
            "a" : {
                "key" : "2",
                "value" : "test"
            }
        }
    }
    

    The query MyDoc.objects(data__a__value="test").first() succeeds while the query MyDoc.objects(data__key__value="test").first() fails with mongoengine.errors.InvalidQueryError: Cannot resolve field "value"

    opened by evg-allegro 0
  • QuerySet class in MongoEngine does not have .model key as the django.db.models.query.QuerySet.model in

    QuerySet class in MongoEngine does not have .model key as the django.db.models.query.QuerySet.model in

    QuerySet class in MongoEngine does not have .model key as the in the QuerySet class as defined in django.db.models.query.QuerySet.

    adding this field to queryset on initialization could allow for better compatibility with DRF and related packages.

    opened by oussjarrousse 1
  • Error with ReferenceField pointing to the abstract document

    Error with ReferenceField pointing to the abstract document

    We've run into an issue where reload, save, and update throw an error when they dereference the abstract field from a ReferenceField.

    It works fine when you initially save the object or get it from the DB but fails if you modify and then save it.

    It also works if you use setattr to set the attribute.

    Since we use an abstract document, it doesn't exist in the database, so dereference method fails.

    Traceback

    >>> demo()
    Company
    456
    changed to the second title
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
      File "/code/issue.py", line 55, in demo
        issue.reload()  # works
      File "/app/venv/lib/python3.10/site-packages/mongoengine/document.py", line 745, in reload
        self._qs.read_preference(ReadPreference.PRIMARY)
      File "/app/venv/lib/python3.10/site-packages/mongoengine/queryset/base.py", line 844, in select_related
        return queryset._dereference(queryset, max_depth=max_depth)
      File "/app/venv/lib/python3.10/site-packages/mongoengine/dereference.py", line 102, in __call__
        self.object_map = self._fetch_objects(doc_type=doc_type)
      File "/app/venv/lib/python3.10/site-packages/mongoengine/dereference.py", line 197, in _fetch_objects
        references = get_db()[collection].find({"_id": {"$in": refs}})
      File "/app/venv/lib/python3.10/site-packages/pymongo/database.py", line 237, in __getitem__
        return Collection(self, name)
      File "/app/venv/lib/python3.10/site-packages/pymongo/collection.py", line 207, in __init__
        raise TypeError("name must be an instance of str")
    TypeError: name must be an instance of str
    

    Example

    from mongoengine import StringField, Document, ReferenceField
    
    
    class Owner(Document):
        meta = {"abstract": True}
        name = StringField()
    
    
    class Company(Owner):
        # meta = {"strict": False}
    
        key = StringField()
    
    
    class Issue(Document):
    
        title = StringField(required=True)
        owner = ReferenceField(Owner)  # since Owner is the abstract class; it is not registered in the database
    
    
    def demo():
        company = Company(name="Company", key="456")
        company.save()
        issue = Issue(title="image", owner=company).save()
    
        print(issue.owner.name)  # prints "Company"
        print(issue.owner.key)  # prints "456"
    
        setattr(issue, "title", "second title")
        issue.save()
        print("changed to second title")
    
        issue.reload()  # fails
    
        # also fails
        issue.text = "another text"
        issue.save()  # fails
    
    opened by gerlv 0
  • Calling len() on QuerySet during iteration will end iteration prematurely

    Calling len() on QuerySet during iteration will end iteration prematurely

    Calling len() on a QuerySet object will fetch and cache all results from the database, returning the length of the cached results. If len() is called during iteration, it will cause the iteration to end prematurely. An example:

    function test_len(run_len):
        # A collection with enough documents that the cursor will perform multiple db fetches (N > 100).
        docs = SomeDocument.objects()
        run_len = False
        i = 0
        for doc in docs:
            i = i + 1
            _ = run_len and len(docs)  # This causes the issue.
    
        assert i == docs.count(), i  # When run_len is True, i == 100 < docs.count().
    
    test_len(False)  # Works as expected.
    test_len(True)   # Demonstrates issue.
    

    This issue was introduced in commit https://github.com/MongoEngine/mongoengine/commit/9251ce312bc0545d3b86224e35a913029a86695e while resolving issue https://github.com/MongoEngine/mongoengine/issues/247.

    opened by geowtf 0
  • EmbeddedDocumentList in nested embededded document save() does not find the parent document

    EmbeddedDocumentList in nested embededded document save() does not find the parent document

    save() not working in an EmbeddedDocumentList in nested embedded document, as _instance is an EmbeddedDocument instead of Document

    Reproducer:

    class TestK2(EmbeddedDocument):
      values = EmbeddedDocumentListField(StringField, default=[])
    
    class TestK1(EmbeddedDocument): 
      k2 = EmbeddedDocumentField(TestK2)
    
    class Main(Document):
      part = EmbeddedDocumentField(TestK1)
    
    def main(): 
      main = Part()
      main.part.k1.k2.values.save()  # AttributeError: TestK1 has no attribute 'save'
    

    I would assume that nested EmbeddedDocuments should have _instance pointing to the Document instance and _parent pointing to the parent doc (embedded or actual document)

    opened by jvhoffbauer 0
Releases(v0.25.0)
  • v0.25.0(Dec 28, 2022)

  • v0.24.2(Jul 17, 2022)

  • v0.24.1(Mar 21, 2022)

    What's Changed

    • update dependency specifier to allow pymongo 4.x by @terencehonles in https://github.com/MongoEngine/mongoengine/pull/2630
    • elaborate_authentication_breaking_change_authsource by @bagerard in https://github.com/MongoEngine/mongoengine/pull/2634
    • Don't use deprecated property for emptiness check by @arthurio in https://github.com/MongoEngine/mongoengine/pull/2633
    • Prepare release 0 24 1 by @bagerard in https://github.com/MongoEngine/mongoengine/pull/2637

    New Contributors

    • @arthurio made their first contribution in https://github.com/MongoEngine/mongoengine/pull/2633
    Source code(tar.gz)
    Source code(zip)
  • v0.24.0(Feb 20, 2022)

  • v0.23.0(Mar 4, 2021)

  • v0.22.1(Dec 16, 2020)

  • v0.22.0(Dec 14, 2020)

  • v0.21.0(Nov 19, 2020)

  • v0.20.0(May 2, 2020)

  • v0.19.1(Jan 4, 2020)

  • v0.19.0(Dec 24, 2019)

  • v0.18.2(Jun 25, 2019)

  • v0.18.1(Jun 18, 2019)

  • v0.18.0(Jun 12, 2019)

  • v0.17.0(Mar 11, 2019)

  • v0.16.2(Nov 21, 2018)

  • v0.16.1(Nov 14, 2018)

  • v0.15.3(Jul 16, 2018)

  • v0.15.1(Apr 17, 2018)

  • v0.15.0(Apr 6, 2018)

  • v0.14.3(Oct 1, 2017)

  • v0.14.1(Oct 1, 2017)

    • Removed SemiStrictDict and started using a regular dict for BaseDocument._data #1630
    • Added support for the $position param in the $push operator #1566
    • Fixed DateTimeField interpreting an empty string as today #1533
    • Added a missing __ne__ method to the GridFSProxy class #1632
    • Fixed BaseQuerySet._fields_to_db_fields #1553
    Source code(tar.gz)
    Source code(zip)
  • v0.14.0(May 8, 2017)

    This release includes a few bug fixes and a significant code cleanup in an ongoing effort to make this codebase much healthier. Primary changes:

    • BREAKING CHANGE: Removed the coerce_types param from QuerySet.as_pymongo #1549
    • POTENTIAL BREAKING CHANGE: Made EmbeddedDocument not hashable by default #1528
    • Improved code quality #1531, #1540, #1541, #1547
    Source code(tar.gz)
    Source code(zip)
  • v0.13.0(Apr 16, 2017)

    This release adds UTF-8 support to the EmailField along with other validation tweaks (#1527).

    Previously, email addresses containing Unicode characters didn't work at all. Now, domains with Unicode characters are supported out of the box and similar validation on the user part can be explicitly enabled. Additionally, you can enable an optional validation of IP-based domain parts (e.g. "user@[127.0.0.1]"), and you can have a whitelist of otherwise invalid domains (e.g. "root@localhost").

    Source code(tar.gz)
    Source code(zip)
  • v0.12.0(Apr 7, 2017)

    This is primarily a bugfix release, but it may also introduce breaking changes if you relied on a previously broken implementation. See https://mongoengine-odm.readthedocs.io/upgrade.html before upgrading.

    • POTENTIAL BREAKING CHANGE: Fixed limit/skip/hint/batch_size chaining #1476
    • POTENTIAL BREAKING CHANGE: Changed a public QuerySet.clone_into method to a private QuerySet._clone_into #1476
    • Fixed the way Document.objects.create works with duplicate IDs #1485
    • Fixed connecting to a replica set with PyMongo 2.x #1436
    • Fixed using sets in field choices #1481
    • Fixed deleting items from a ListField #1318
    • Fixed an obscure error message when filtering by field__in=non_iterable. #1237
    • Fixed behavior of a dec update operator #1450
    • Added a rename update operator #1454
    • Added validation for the db_field parameter #1448
    • Fixed the error message displayed when querying an EmbeddedDocumentField by an invalid value #1440
    • Fixed the error message displayed when validating unicode URLs #1486
    • Raise an error when trying to save an abstract document #1449
    Source code(tar.gz)
    Source code(zip)
  • v0.11.0(Dec 13, 2016)

    This release includes a major re-haul of MongoEngine's code quality and introduces a few breaking changes. It also touches many different parts of the package and although all the changes have been tested and scrutinized, you're encouraged to thoroughly test the upgrade.

    First breaking change involves renaming ConnectionError to MongoEngineConnectionError. If you import or catch this exception, you'll need to rename it in your code.

    Second breaking change drops Python v2.6 support. If you run MongoEngine on that Python version, you'll need to upgrade it first.

    Third breaking change drops an old backward compatibility measure where from mongoengine.base import ErrorClass would work on top of from mongoengine.errors import ErrorClass (where ErrorClass is e.g. ValidationError). If you import any exceptions from mongoengine.base, change it to mongoengine.errors.

    Lastly, we fixed absent rounding for DecimalField when force_string is set (#1103).

    Source code(tar.gz)
    Source code(zip)
  • v0.10.9(Dec 11, 2016)

Pony Object Relational Mapper

Downloads Pony Object-Relational Mapper Pony is an advanced object-relational mapper. The most interesting feature of Pony is its ability to write que

null 3.1k Jan 1, 2023
SQLModel is a library for interacting with SQL databases from Python code, with Python objects.

SQLModel is a library for interacting with SQL databases from Python code, with Python objects. It is designed to be intuitive, easy to use, highly compatible, and robust.

Sebastián Ramírez 9.1k Dec 31, 2022
A pure Python Database Abstraction Layer

pyDAL pyDAL is a pure Python Database Abstraction Layer. It dynamically generates the SQL/noSQL in realtime using the specified dialect for the databa

null 440 Nov 13, 2022
Rich Python data types for Redis

Created by Stephen McDonald Introduction HOT Redis is a wrapper library for the redis-py client. Rather than calling the Redis commands directly from

Stephen McDonald 281 Nov 10, 2022
A Python Library for Simple Models and Containers Persisted in Redis

Redisco Python Containers and Simple Models for Redis Description Redisco allows you to store objects in Redis. It is inspired by the Ruby library Ohm

sebastien requiem 436 Nov 10, 2022
The ormar package is an async mini ORM for Python, with support for Postgres, MySQL, and SQLite.

python async mini orm with fastapi in mind and pydantic validation

null 1.2k Jan 5, 2023
Solrorm : A sort-of solr ORM for python

solrorm : A sort-of solr ORM for python solrpy - deprecated solrorm - currently in dev Usage Cores The first step to interact with solr using solrorm

Aj 1 Nov 21, 2021
Python 3.6+ Asyncio PostgreSQL query builder and model

windyquery - A non-blocking Python PostgreSQL query builder Windyquery is a non-blocking PostgreSQL query builder with Asyncio. Installation $ pip ins

null 67 Sep 1, 2022
A PostgreSQL or SQLite orm for Python

Prom An opinionated lightweight orm for PostgreSQL or SQLite. Prom has been used in both single threaded and multi-threaded environments, including en

Jay Marcyes 18 Dec 1, 2022
ORM for Python for PostgreSQL.

New generation (or genius) ORM for Python for PostgreSQL. Fully-typed for any query with Pydantic and auto-model generation, compatible with any sync or async driver

Yan Kurbatov 3 Apr 13, 2022
A new ORM for Python specially for PostgreSQL

A new ORM for Python specially for PostgreSQL. Fully-typed for any query with Pydantic and auto-model generation, compatible with any sync or async driver

Yan Kurbatov 3 Apr 13, 2022
A Python Object-Document-Mapper for working with MongoDB

MongoEngine Info: MongoEngine is an ORM-like layer on top of PyMongo. Repository: https://github.com/MongoEngine/mongoengine Author: Harry Marr (http:

MongoEngine 3.9k Jan 8, 2023
Async ODM (Object Document Mapper) for MongoDB based on python type hints

ODMantic Documentation: https://art049.github.io/odmantic/ Asynchronous ODM(Object Document Mapper) for MongoDB based on standard python type hints. I

Arthur Pastel 732 Dec 31, 2022
Beanie - is an Asynchronous Python object-document mapper (ODM) for MongoDB

Beanie - is an Asynchronous Python object-document mapper (ODM) for MongoDB, based on Motor and Pydantic.

Roman 993 Jan 3, 2023
Fully Automated YouTube Channel ▶️with Added Extra Features.

Fully Automated Youtube Channel ▒█▀▀█ █▀▀█ ▀▀█▀▀ ▀▀█▀▀ █░░█ █▀▀▄ █▀▀ █▀▀█ ▒█▀▀▄ █░░█ ░░█░░ ░▒█░░ █░░█ █▀▀▄ █▀▀ █▄▄▀ ▒█▄▄█ ▀▀▀▀ ░░▀░░ ░▒█░░ ░▀▀▀ ▀▀▀░

sam-sepiol 249 Jan 2, 2023
Working Time Statistics of working hours and working conditions by industry and company

Working Time Statistics of working hours and working conditions by industry and company

Feng Ruohang 88 Nov 4, 2022
A Pythonic, object-oriented interface for working with MongoDB.

PyMODM MongoDB has paused the development of PyMODM. If there are any users who want to take over and maintain this project, or if you just have quest

mongodb 345 Dec 25, 2022
MongoDB data stream pipeline tools by YouGov (adopted from MongoDB)

mongo-connector The mongo-connector project originated as a MongoDB mongo-labs project and is now community-maintained under the custody of YouGov, Pl

YouGov 1.9k Jan 4, 2023
Backend, modern REST API for obtaining match and odds data crawled from multiple sites. Using FastAPI, MongoDB as database, Motor as async MongoDB client, Scrapy as crawler and Docker.

Introduction Apiestas is a project composed of a backend powered by the awesome framework FastAPI and a crawler powered by Scrapy. This project has fo

Fran Lozano 54 Dec 13, 2022
Caretaker 2 Jun 6, 2022