This is an automated email from the ASF dual-hosted git repository.
jooger pushed a change to branch jdbc_over_thin_sql
in repository https://gitbox.apache.org/repos/asf/ignite-3.git
omit 6d2fc42a132 Merge branch 'main' into jdbc_over_thin_sql
omit ffe62e80175 IGNITE-26276 Sql. Jdbc. Add new implementation for
ResultSetMetadata (#6488)
omit d22a009cdf8 IGNITE-26087 Ability to obtain results of a
multi-statement query execution using the internal thin client SQL API. (#6397)
omit 48832298c4e IGNITE-26086 Ability to restrict query execution by type
in thin client SQL API (#6383)
new 1a5290cf8da IGNITE-26086 Ability to restrict query execution by type
in thin client SQL API (#6383)
new 3d2a8ebaa74 IGNITE-26087 Ability to obtain results of a
multi-statement query execution using the internal thin client SQL API. (#6397)
new d7e92ce689d IGNITE-26276 Sql. Jdbc. Add new implementation for
ResultSetMetadata (#6488)
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 (6d2fc42a132)
\
N -- N -- N refs/heads/jdbc_over_thin_sql (d7e92ce689d)
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.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
