gianmarco

It seems that the entityManager gets confused and tries to INSERT a new row instead of UPDATE'ing the correct one. Setting "command" as a unique field in the database is...

Is there any update about this issue?

I have the same suspicion, especially because all other associations work perfectly. Digging more I have found that it's caused by: ```php #[UniqueEntity(fields: [................, "products"], message: "......", ignoreNull: false] ```...

Ok, thanks. But, anyway, shouldn't we test if $assoc is not null (which might be, according to the method's signature) before accessing $assoc['isOwningSide'] ? Or is it overengineering? Feel free...

Hi, any news about this issue?

Same problem here. It seems to get worse after reloading VS Code