Changelog History
Page 1
-
v1.3.6 Changes
June 06, 2020๐ Thanks to @tylerganter for the pull request to significantly improve the performance of update_many.
๐ In this release:
- ๐
update_many
now uses bulk writes which significantly improves the performance of calling update_many. unset
andunset_methods
have now been added to theFrame
class.- A fix has been applied to the
ElemMatch
function which previously would raise an error if a raw condition was given instead of aCondition
instance.
- ๐
-
v1.3.5 Changes
January 16, 2020It's now possible to set the collection options for a frame within a given context, such as:
with MyFrame.with\_options(read\_preference=ReadPreference.SECONDARY): my\_frame = MyFrame.one()
๐ This release also sees a move to pymongo>=3.9.0 requirements.
-
v1.3.4 Changes
May 25, 2019This release has moved the minimum pymongo requirement to 3.8+. To support this change we've replaced a number of pymongo deprecated method calls, including
update
withupdate_one
andcount
withcount_documents
orestimated_document_count
. This does not change theupdate
andcount
methods / API for MongoFrames.๐ In addition I fixed an issue where using
$slice
in a reference projection wasn't correctly, for example in the expression:projection={ 'name': True, 'show\_date\_str': True, 'leads': { '$ref': User, '$slice': 1, 'first\_name': True, 'last\_name': True } }
This now correctly selects the first Id in the leads field to use as a reference when selecting the assoicated users
-
v1.3.3
February 24, 2019 -
v1.3.2
February 19, 2019 -
v1.3.1
February 07, 2019 -
v1.3.0 Changes
February 06, 2019๐ Previous to this release projections within
$sub
or$sub.
where simply ignored and the projection was converted to True for the key, for example:lairs = Lair.many( projection={ '\_id': True, 'inventory': { '$sub': Inventory, 'gold': True } )
Previously used the projection:
{ '_id: True, 'inventory': True }
๐ In this release this will now project to:
{ '_id: True, 'inventory.gold': True }
๐ NOTE: This release is a minor release as whilst this should effect existing code if you've previous been setting projections (which simply were ignored before) this could potentially break this code.
-
v1.2.14
December 17, 2018 -
v1.2.13 Changes
August 15, 2018For example this is now possible:
projection={ 'employees': { '$ref': Employee, '$slice': 2, 'name': True } }
So get the first 2 employee Ids in an array of employee Ids stored against the field
employees
and project them as Employee documents selecting only the name field for each. -
v1.2.12
August 13, 2018