Šimon Kandráč

> I need some time to answer, this has a few internal implications that could prevent this Can I somehow help with that? Are those implications related to the virtual...

Hello, just a friendly reminder since it's been some time, it would be really awesome if this could get to 3.4 release.

> 1. For regular properties, for post commit id generators, you need to leave the `id` property nullable at least until the first flush, because this code execution order requires...

@beberlei I have implemented [an exception for ID columns](https://github.com/doctrine/orm/pull/11814/files#diff-546eb60e406d89362faee89bd404217c4f74305586b791ad1198ff6405c5fdbcR1216) (also covered by tests), even though I don't think it's a good idea to introduce inconsistent behavior and encourage having `$id`...

> The uninitialized state is a footgun. Benjamin is right, we have to allow auto-increment ID fields to be nullable without mapping them to nullable fields in the schema. Ok,...

@greg0ire @SenseException I'm going to do a rebase, but I'm unsure how to proceed because of possible BC break related to https://github.com/doctrine/orm/pull/12108, there was a short discussion satarted by @morozov...

Hello, I would really appreciate it if someone could reply. I mentioned multiple people who know what’s going on, and I even asked about it on Slack two months ago,...

@jacobbednarz would you please merge this and tag new version? The library is not compatible with PHP 8.4 as of this moment, it's been 4 months since PHP 8.4 was...

Well, when someone updates from 2.0 to 3.0, BC breaks are expected, I bet that most people will have not a single line in migration, since now they are forced...

That special cases with `$id` can be resolved with some exception for `Id`? That `Id` just can't be nullable in any scenario? > This means that there has to be...