Consider simplifying the session execution logic to always run an autoflush, independently of the fact that an ORM statement is being executed or not.
Since the v2 syntax is using the same paradigm for both core and orm execution, with the addition of the orm enabled select in 1.4 and the orm enabled dml statements (insert, update, delete) in v2, the current logic of conditionally flushing the session only when an orm related thing is executed is a bit hard to properly define, and may cause confusion on what is and what isn't an orm statement.
For example: #9805
Consider simplifying the session execution logic to always run an autoflush, independently of the fact that an ORM statement is being executed or not.
Since the v2 syntax is using the same paradigm for both core and orm execution, with the addition of the orm enabled select in 1.4 and the orm enabled dml statements (insert, update, delete) in v2, the current logic of conditionally flushing the session only when an orm related thing is executed is a bit hard to properly define, and may cause confusion on what is and what isn't an orm statement.
For example: #9805