Does the planned implementation of this feature allow for multiple strategies to be used in conjunction? For example using a database strategy to determine which host to connect to with a discriminator strategy used against tenant partitioned data within each table?

Also, I don't see in your considerations applying the discriminator restriction to update and delete statements, which would be needed to fully support a partitioning scheme (aka Mysql partitioned tables behave badly when the partition key is not used as part of an update).

And finally have there been any commits for this work as of yet? I am working on implementing the above in the 4.3.6 code base and although I've managed to cover most of the primary entity cases the lazy collection loading part is not working.