Emmanuel Bernard Well that is really a series of READMEs that eventually conclude "this is not implemented". Lol - thanks It does show that patch for the most trivial part of implementing that feature (which Connection to use) but that's it.

Jason Northcote That's awesome. I'd definitely be interested in having a look and helping get that completed. To some of your specific questions...

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?

No, I had not planned on that. What's the use case exactly?

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).

Yes, I just took it as obvious

And finally have there been any recent commits for this work?

No. I had (personally) been putting this off as part of the larger annotation binding (that jandex-binding version) rework. But if you have a lot of the work on this done, that obviously changes the resources argument