Marc J. Schmidt

> @marcj I will be unavailable for a week now, but I can finish the PR after that, maybe you can collect feedback for me until then. I will then...

The ORM has no multi-tenancy manager functionality per se, but you can create your own pool layer since the `Database` instance can be quickly created however you want. ```typescript import...

Ah I see, so you don't want to have a new db driver instance for each tenant because there might be a lot. That's currently not supported for Mongo out...

> when having a small number of tenants If demand grows, we can build that in natively. Wouldn't be much work, but definitely touches a few places. Thank you! If...

Yeah, can work perfectly fine if you are consistent. Although Mongo has also some kind of "migrations", for the creation of indices. Not in the form of SQL, but you...

I see, yes indeed the internals might change and we could add instead a simpler API for adding checkers/serializers for simple class types.

Yeah I had such a group mechanism already on my list but didn't find the time yet. Totally makes sense! Indeed `@f.exclude` is on compile level, what you need is...

@rafaferry unfortunately, not that straightforward since `i` in `partial` can be a deep path, e.g. `user.settings.color`, so that loop is not the right place. It needs to be in `JitPropertyConverter.convert()`...

@j, do you have an example/pseudo-code? I don't completely get what you mean.

@j could you post an actual detailed use-case? I can't come up with one. > Both would conflict Why? They would have each their own class definitions and thus their...