Hi all,
I also would like to reiterate that Quarkus has no particular support for
multi-tenancy with options 1 or 2: unless there are only a handful of
datasources to use, and they can all be fixed at build time (which I think
is not the case here), we'd need to manage the datasources and their
co
Hi Mike,
Thanks for the historical context, that is really helpful. And I completely
agree with your last paragraph, and especially this:
My preference would be to make this an immutable class that has the
> principal entity and all active principal roles all in the constructor.
I was arriving
On Mon, Apr 21, 2025 at 6:34 PM Yufei Gu wrote:
> Thanks Pierre for driving this. The plan sounds good to me! A side
> question, are we planning to make a benchmark pipeline against the main
> branch?
I think it would be good to setup a pipeline against `main`, yes. Although
I am not sure whic
To clarify, Polaris *does* support multi-tenancy. What’s currently limited
with Option 1 is *account-level* multi-tenancy specifically in the context
of EclipseLink.
1. *Multi-account support* is most relevant when a vendor wants to
commercialize Polaris and offer it as a service to customer
