On MariaDB, It updates JSON column which not changed. about mikro-orm HOT 11 CLOSED

Let's keep this open, I'll first look if we can fix this as it should generally work the way you tried. It's just that many people really don't need this option, and generally speaking, you should rather not combine it with explicit constructor usage.

from mikro-orm.

This is caused by forceEntityConstructor, why do you want to use that? You shouldn't need this unless you use native private properties in your entity. Do you understand em.create uses the constructor regardless of this option? It's only about using constructor for creating managed entity instances.

from mikro-orm.

We are using it because of private properties in entity. Actually, We are using EntitySchema for our code conventions on NestJS. (model class, repository pattern, interface inject, etc.) Is it the only solution to solve this situation that disable forceEntityConstructor and avoid private properties?

from mikro-orm.

Private properties as in private TS keyword or native private properties as in #propName? This is only about the latter.

from mikro-orm.

I checked it again, the problem is readonly properties not private. I made new commit about it on reproduce repository.

from mikro-orm.

That flag has nothing to do with readonly modifier, you shouldnt need that in this test. Readonly modifier is a ts thing, it has no effect on runtime, and this flag has no type level effect.

from mikro-orm.

Thanks for feedback! I confused because of the original source code in companies. It occurs on property with =. I made new commit about it on reproduce repository, but I can figure out the reason is Object.create.
Then how can we solve that? On the original, we are using it like logger = new Logger('User'); but in this case this.logger is undefined.

from mikro-orm.

You can use @OnInit hook

https://mikro-orm.io/docs/events#hooks

from mikro-orm.

I got it. For the same reason, all of method in class with arrow function are undefined too. I should change them all... 😵‍💫

from mikro-orm.

Do you have an actual reason to use arrow functions there? Turn them into actual methods and this problem disappears too.

from mikro-orm.

Yeah, It didn't have an actual reason about it... Just the reason it uses less lines.

isDisabled = () => this.status === 'progress';

isDisabled() {
  return this.status === 'progress';
}

Thanks for the reply!

from mikro-orm.