Mongosql

Latest version: v2.0.15.post1

Safety actively analyzes 629811 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

2.0.8

* `CrudView._method_create_or_update_many()`: saving many objects at once
* `MongoQuery.options()`: `no_limit_offset=True` lets you disable limits & offsets for a specific query
* Tested with SqlAlchemy 1.3.9-10

2.0.7

* `project`: now allow using a string of field names, separated by whitespace. Example: `{project: "name age weight"}`
* `saves_relations`: now possible to differentiate a value not provided from a provided `None`
* Better sqlalchemy error messages: a new `mongosql.exc.RuntimeQueryError` provides more details about internal errors.

Example:
> mongosql.exc.RuntimeQueryError: Error processing MongoQuery(Assignment -> Category).join: (cryptic sqlalchemy message)
* Bugfix: compilation of dialect-specific clauses used to fail with some JOINs
* Bugfix: `max_items` + `force_filter` used to cause trouble because MongoSQL could not make the correct decision
that a nested query is necessary

2.0.6

* `bundled_project` are now loaded quietly (meaning, they are loaded, but not included into the projection)
* `MongoQuerySettingsDict.pluck_from()`: now skips the `max_items` key because it does not make sense when inherited
* Bugfix: in some cases, the `projection` property returned invalid results
* Bugfix: when the `join` operation includes two relationships that are LEFT JOINed, the query is not broken anymore.

2.0.5

* `ensure_loaded` setting for projections

2.0.4

* `filter`: new `$prefix` operator
* `AssociationProxy` support for `project` and `filter`
* `MongoQuery.get_final_query_object()` method for debugging
* Project Handler: the new `default_projection` behavior lets you build APIs that return no fields by default:
the API user will have to require every field explicitly.

2.0.3

* CrudHelper is not able to save `property` values: welcome `writable_properties`!
* Fix: `bundled_project` now takes care of `force_include`d fields as well
* Recommendation when a legacy column is removed: use `legacy_fields` together with `force_include`
on a `property` that fakes the missing column or relationship.
* CrudHelper now removes `legacy_fields` from the input dict
* `legacy_fields` are now included into all projections generated by `project` and `join` handlers

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.