You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@grails.apache.org by GitBox <gi...@apache.org> on 2026/10/21 08:48:56 UTC
[GH] (grails-core/fix/gorm-without-tenant-marker-7.0.x): Workflow run "CI" failed!
The GitHub Actions job "CI" on grails-core.git/fix/gorm-without-tenant-marker-7.0.x has failed.
Run started by GitHub user matrei (triggered by matrei).
Head commit for run:
14eaf0ce236a706077380c414e0d90ca311a978f / Mattias Reichel <ma...@gmail.com>
Run without a tenant only inside Tenants.withoutId
With DISCRIMINATOR multi-tenancy, only Tenants.withoutId and
@WithoutTenant run without a tenant. A tenant id of DEFAULT from a
resolver or from withId is a tenant id like any other, and inside
withoutId, Tenants.currentId() returns DEFAULT while withCurrent and
@CurrentTenant keep running without a tenant. The new
Tenants.isWithoutId() and Tenants.isWithoutId(datastore) tell whether
the current code runs without a tenant id.
A tenant resolver that returns null causes a TenantNotFoundException.
GORM for Hibernate restricts a collection of a multi-tenant entity to
the current tenant when it is loaded lazily or fetched by join, also
when it is a many-to-many collection or a query fetches it by join
through another association, and load and proxy of a multi-tenant
entity run a query, as get does.
Before a query on an entity that isn't multi-tenant but has a
collection of a multi-tenant entity, criteria queries included, GORM
for Hibernate activates the tenant filter when there is a current
tenant. A query on such an entity that the tenant resolver runs while
GORM resolves the tenant does not call the resolver again.
Report URL: https://github.com/apache/grails-core/actions/runs/39560138480
With regards,
GitHub Actions via GitBox