Alexander M. Turek
Alexander M. Turek
Thank you for your PR. Please _always_ write tests that cover your change. What problem does this change fix? Note that the type parameter has been removed from DBAL.
> I indeed use MySQL. So the problem is executing a transactional (manually setting isTransactional to false) + a non-transactional (default behaviour) in 1 migration run. We can't mix them...
@beberlei @greg0ire I've spoken to @soyuka about this issue. The issue is that app tries to persist lazy objects as new records. Those are lazy objects that are _not_ Doctrine...
> Regardless of the answer, it seems that we should attempt to detect whether objects are lazy or not. Do we have a way to do that that is reliable...
If I pass an object to the ORM via the `persist()` method, I believe I do that with the intention of having it read by the ORM. So maybe initializing...
Can you elaborate why you need this change? A functional test could also help me understand your use-case.
Not sure if the DBAL type system is a good fit for this feature. Maybe we should implement this in the ORM instead, like we did with `enumType`.
> If the ORM layer is indeed the more appropriate place for this feature, I'd be happy to have the issue transferred there Done.