orm module has been renamed odm for object data mapper. This was a painful change
with the vast majority of files affected. But it is better to get terminology
right at this stage rather than later.stdnet.odm.ManyToManyField which now uses a through model
for building many to many relationships.
This is the only backward incompatible change both in terms of API and database scema.field lookups <range-lookups> gt, ge, lt and le.stdnet.lib.redis.PrefixedRedis.stdnet.odm.CompositeIdField to handle situations where each
combination of given set of :class:stdnet.odm.Field must be unique.stdnet.odm.ForeignKey fields.stdnet.odm.Session for managing transactions in the object
data mapper.stdnet.backends to the :mod:stdnet.odm module.stdnet.odm.Query.load_only and :meth:stdnet.odm.Query.dont_load
methods for loading a subset of a model fields.
This can improve performance by reducing the amount of
data transferred from the server to the client.
Check the :ref:performance tips <performance-loadonly> regarding the
new feature.stdnet.odm.Query.load_related for loading related
fields of a queryset with a single database query. This can have huge
:ref:performance benefits <performance-loadrelated> when you know you are
going to access the related field in your model.exclude method was not implemented.stdnet.odm.PickleObjectField uses the pickle protocol 2 for compatibility
between python 2 and python 3.save and delete method of model instances.stdnet.odm.StdModel.tojson method for obtaining JSON representation
of model instances.stdnet.odm.ForeignKey fields are stored at sets with
keys obtained from the field attrname rather than name.stdnet.odm.StdModel.clone method for cloning model instances.transactions <model-transactions> to be used with
:ref:remote data structures <model-structures> and
:ref:structured fields <model-field-structure>.stdnet.apps.stdnet.utils.dates.stdnet.utils.path.stdnet.odm.ManyToMany.through models via
the :func:stdnet.odm.all_models_sessions function (issue #48).stdnet.odm.TS structure... _vers06: