dummy $options to avoid tests from failing if you use options for regex
mim: better _project
mim: bugged $and if used together with $or
mim: better _project
0.5.6
Support python 3.5 and 3.6 in tox
Recursively convert MatchDoc and MatchList types, so a deeply nested value will match correctly still
News pointer to master
Support python 3.6 in tox
Recursively convert MatchDoc and MatchList types, so a deeply nested value will match correctly still
Update news
Version 0.6.5
when setting documents with lists, allow integer notation
fix the case where '_id' is excluded from the fields while performing an update.
find_one_and_delete should actually delete
Version 0.6.4
Fix with missing keys
Version 0.6.3
mim text search: better text indexes gathering
schema validation: convert datetime.date to datetime.datetime
Merge commit '79e29803496be644d309c0b4237f87f5f946a001'
schema validation: convert datetime.date to datetime.datetime
mim text search: better text indexes gathering
Version 0.6.2
added dummy $search operator in mim
Merge commit '62fe4f5ee70299682eab567a0654eefb6ca7a7fd'
Merge branch 'master' of ssh://git.code.sf.net/p/merciless/code
Add Python3.5 to tox
Match regex within text, not just at begin
Version 0.6.1
if _id in collection._data.keys(): probably wants to be replaced with if _id in collection._data
added dummy $search operator in mim
added rewind to ODMCursor
added rewind to ODMCursor
I haven't used text indexes, but give this a try. I think it might work. Change 'text' to 'hashed' for hashed index type. class __mongometa__: custom_indexes = [ dict(fields=('doc_post.segment',), direction='text'), ]
I am trying to create a text index on a nested document. There is no documented way to specify a 'text' or a 'hashed' index in ming. Is this automatically deduced? When i create an index with the default, it throws 'WiredTigerIndex::insert: key too large to index' exception. On further reading, it seems that the default indexing is limited to documents less than 1024 bytes. For all else, we need to specify either a 'text' or a 'hashed' index. what is the proper way to do that with ming MappedClass...
I am trying to create a text index on a nested document. There is no documented way to specify a 'text' or a 'hashed' index in ming. Is this automatically deduced? When i create an index with the default, it throws 'WiredTigerIndex::insert: key too large to index' exception. On further reading, it seems that the default indexing is limited to documents less than 1024 bytes. For all else, we need to specify either a 'text' or a 'hashed' index. what is the proper way to do that with ming MappedClass...
I am trying to create a text index on a nested document. There is no documented way to specify a 'text' or a 'hashed' index in ming. Is this automatically deduced? When i create an index with the default, it throws 'WiredTigerIndex::insert: key too large to index' exception. On further reading, it seems that the default indexing is limited to documents less than 1024 bytes. For all else, we need to specify either a 'text' or a 'hashed' index. what is the proper way to do that with ming MappedClass...
I am trying to create a text index on a nested document. There is no documented way to specify a 'text' or a 'hashed' index in ming. Is this automatically deduced? When i create an index with the default, it throws 'WiredTigerIndex::insert: key too large to index' exception. On further reading, it seems that the default indexing is limited to documents less than 1024 bytes. For all else, we need to specify either a 'text' or a 'hashed' index. what is the proper way to do that with ming MappedClass...
ChangeLog for 0.6.0
Version 0.6.0
Ensure duplicated keys are detected on upsertions
Support for filters on distinct
Provide drop_indexes
Simulate collstats
Tweak result
Provide insert_one and insert_many results
Fix remove and provide implementation
Provide UpdateResult too
Fix skip and limit being passed as 0 and provide stub add_option to cursor
Apply consistent index encoding everywhere
Support for delete_many and delete_one results
Fix delete tests
Support for setOnInsert
Allow idexing whole subdocuments
Minor tweaks for pymongo3 compatibility
Improve compatibility with recent mongodbs
Merge master into pymongo-30
0.5.5
MIM: regex matching against None or non-existen...
ming 0.5.4 ignore 'if_missing' on subdocuments
ming-0.5.4 (and 0.5.0) tests fail with python2.7, pass with 3.4
Support distinct() on the ming cursor objects (...
0.5.4
Upgrade to compatibility with pymongo3.2
That's not strictly a bug as it's the currently documented behaviour ( http://ming.readthedocs.org/en/latest/polymorphism.html#querying-polymorphic-entities...
Same problem here! In my eyes, a query on a subclass should only return instances...
Remove use_greenlets and gevent sleep, just use...
Merge branch 'master' into pymongo-30
Fix MIM read/write concern value on pymongo3
On Python3 Binary actually decodes to bytes
0.5.3
Looks like there are projects referencing ORM n...
oops, forgot forced True while testing
MIM fields didn't work with tuples
Add support for readthedocs.org, when compiling...
Add .create / ._from_doc speedups to News
Fix mutating object also mutates the original_d...
Recover ORMSession, ThreadLocalORMSession and C...
Minor doc touchups
As Mapper.create might be called on manually cr...
Documents were actually validated three times w...
typo
More docstrings, added Mapper.ensure_all_indexe...
Add documentation on custom schemas and custom ...
Invalid state is usually just None, provide def...
Major refactoring of documentation, still pendi...
Remove cog dependency, replaced with a sphinx d...
fields parameter is named projection on pymongo...
Initial support for PyMongo3.0, mostly disable ...
use_greenlets is not supported anymore by pymongo
I don't personally have any plans to work on this yet. If someone wants to contribute...
In the mean time I have published Ming 0.5.2 which explicitly specifies pymongo<3.0...
0.5.2
Exclude pymongo 3 until [#27] is resolved
pymongo 3.0 support - Failure to build, caused by test failures
most query methods always raise "'Cursor' object has no attribute 'next'"
I'm getting the same results when using pymongo 3.0, which came out very recently....
Thanks!
update release instructions