(grails-core) branch feat/gorm-registry-neo4j updated (465c3bd77d -> fe887a3d5d)

[bo...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

borinquenkid pushed a change to branch feat/gorm-registry-neo4j
in repository https://gitbox.apache.org/repos/asf/grails-core.git


    omit 465c3bd77d feat: wire Neo4j adapter to GormRegistry O(M+N) scaling
    omit 84a342ee59 feat: wire MongoDB adapter to GormRegistry O(M+N) scaling
    omit c71045dae9 feat: wire Hibernate 5 adapters to GormRegistry O(M+N) scaling
    omit 1dd696ac96 test: add unit and TCK tests for GormRegistry O(M+N) scaling
     add 7dcf26ed39 Fix MongoDB functional tests: fall back to enhancer API factory when no GormApiFactory registered
     add c5d67bd0d1 test: add unit and TCK tests for GormRegistry O(M+N) scaling
     add bde6eff3c2 feat: wire Hibernate 5 adapters to GormRegistry O(M+N) scaling
     add d4c2ea1018 feat: wire MongoDB adapter to GormRegistry O(M+N) scaling
     add fe887a3d5d feat: wire Neo4j adapter to GormRegistry O(M+N) scaling

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   (465c3bd77d)
            \
             N -- N -- N   refs/heads/feat/gorm-registry-neo4j (fe887a3d5d)

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:
 .../groovy/org/grails/datastore/gorm/GormRegistry.groovy    | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)