Sergei Lebedev

Not really, `minimongo` is not _actively_ developed anymore ..

Do we allow two different models work with the same collection? because if yes -- there's no way we can do dereferencing automatically. ``` class Foo(Model): class Meta: collection =...

Actually, I'm thinking restricting the case, when two 2 document types are stored in a single collection -- seems like an easy and simple solution. At least for now.

Quick solution would be to use `assert obj is not None` -- since that's what `pymongo` returns if document wasn't found.

How about we add a dependency on [brownie](https://github.com/DasIch/brownie/blob/master/brownie/datastructures/mappings.py) and implement those folks as `ImmutableDict` subclasses? In fact we can then merge `TypeImmutableDict` and `SchemaImmutableDict` (or whatever we call it) back...

Well, `pymongo` does reconnect in some cases _i'm not yet sure when it does, actually_ -- but try reloading `mongod` with the code running and see what happens :) By...

Okay, this is a little unexpected, I've tried two test cases and everything seems to work fine. Here's the server bit: https://gist.github.com/886138 1. MongoDB crashes with the server running and...

What kind of behaviour would you expect? I'd say `badarg` for both of them.

The first case is fixed in 593cd5c38ca65d4f82c5182e1656af0d49f4958a, the latter is hard to validate, unfortunately. Any suggestions?

1. This will be a separate release. 2. I don't see how `tempo:format(..., {tag, Value})` is different from `tempo:format_now(..., Value)`; plus, the former looks more extensible.