This is an automated email from the ASF dual-hosted git repository.
jamesfredley pushed a change to branch fix/gorm-api-registration-scaling
in repository https://gitbox.apache.org/repos/asf/grails-core.git
omit 0bfd35df3e fix: restore TSM consistency for DATABASE and SCHEMA
per-tenant sessions
omit faf79e6cc7 Merge branch '8.0.x' into fix/gorm-api-registration-scaling
omit 1bdcc9a019 Address GORM API review concurrency
omit 2498f91f60 Cover Hibernate GORM API allocation combinations
omit a6ddce0c16 Reduce GORM API allocation for tenant qualifiers
add ffdd0a5b53 Reduce GORM API allocation for tenant qualifiers to
O(entityCount + tenantCount)
add f02f6432a5 fix: restore TSM consistency for DATABASE and SCHEMA
per-tenant sessions
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (0bfd35df3e)
\
N -- N -- N refs/heads/fix/gorm-api-registration-scaling
(f02f6432a5)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
