Umed Khudoiberdiev
Umed Khudoiberdiev
it's unlikely to be true. Maybe you have something environment-specific or your code doesn't get compiled or something like that. I suggest you to create a minimal reproduction github repository...
Confirmed. Temporary solution is to remove `schema: 'public',` - by default it is already `public` and you can omit it.
@havenchyk its like building a puzzle, find everything and connect each peaces with each other and explain why I came up to this conclusion :) But I'll do it as...
@samjmckenzie yeap, so this kind of "side effects" eager loading brings us - somebody don't want to load it in "reload", somebody don't like that eager isn't flexible and asks...
> What about #2479? It is marked as 0.3.0 but there is no clear solution yet. this is a complex one, we can move it into 0.4.0 but it can...
`save` already does it.
@kamilmysliwiec thanks, your feedback is very important here, since your words are words of thousand nestjs users I believe. First, I would like to say that its on 0.4.0 roadmap...
@liangchunn in 0.x.x second number means breaking changes, so you can treat it as major.
@ryuuji3 it might seem less complicated than it is. > The choice to use eager loading and lazy loading ultimately comes down to the developer. Its our responsibility to impose...
@ematipico new api will be developed instead of current lazy loading mechanizm