Jan Škrášek

> I would just like to know if you like the proposed filtration syntax and what should be these new potential features so we can find out whether api can...

E.g. the issue here is that when there is a nullable relationship, the default `remove` call do a `set null` without any notice. Not a big issue, but may be...

@mskocik It seems your usecase is rather https://github.com/nextras/orm/issues/205. Anyway, the second example is overcomplicated, the relationships are synced, i.e. calling remove is sufficient. No need to set() & persist on...

Currently, I have no intention to implement this. It's hard to do it correctly: if we want to reload entity from serialized version, we have to somehow attach it to...

Not impossible, but the majority of work has to be done in [nextras/dbal](https://github.com/nextras/dbal/issues/83). I did some [initial work in branch](https://github.com/nextras/dbal/commits/sqlite)

For now, you can mock IRepository & Metadata and call onAttach. But I will probably create a Metadata setter for better test usability.

As mentioned in https://github.com/nextras/orm/issues/181#issuecomment-299906224 you may set the Metadata by onAttach. Actually not sure adding setMetadata would be good. It would pollute interface and API for common usage.

The use-case seems pretty reasonable to support directly in Orm. This is possible to do yourself. There are few differences between Orm 3.1 & 4 (master) - but they are...

Postponing to 4.1. But in 4.0 it should be really possible on your own.

I've never used UUID so I'm puzzled a little. What is the issue? From ORM pov there are two things: - mapping -> string to some type in DB ->...