Describe the bug

When creating a new entity and flushing it, the parameters are generated without respecting the property’s nullability configuration. As a result, if a property is defined as nullable and null is explicitly provided, the ORM instead assigns the default value. This causes a behavioral discrepancy compared to previous versions.

Reproduction

I am opening a pr to solve this issues which will have the reproduction included

What driver are you using?

@mikro-orm/postgresql

MikroORM version

6.5.5

Node.js version

22+

Operating system

mac os sequoia

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord.
• The provided reproduction is a minimal reproducible example of the bug.