invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Dummy

Driver Release Note - Internal

Dummy driver 27.0, from 26.0

Build Date Description
26.0.4 22-03-2026 first build of release 26.0
27.0.93 10-11-2026 latest build of release 27.0 at the time of writing

The older end is the first build of release 26.0, not its last, because later builds of 26.0 received ports of changes made for 27.0. The data model of a release is the model that a later build of the same release generated.

  • 5 changes
  • 0 can break a statement
  • 3 groups not available

What Changed, by Group

Every change is in one group: the group answers the question that you ask before you upgrade.

  • Data model
    • –
    • not available
    • Do my statements and views still work?
  • Provider attributes
    • –
    • not available
    • Do I have to change my connection string, provider file or settings?
  • Capabilities
    • –
    • not available
    • What can the driver do with a table?
  • Performance
    • 1
    • Is it faster, and does it call the platform less?
  • Bug fixes
    • 3
    • Is the defect that I met repaired?
  • Enhancements
    • 1
    • What can I do now that I could not?
  • Log-on and platform
    • 0
    • Do I have to log on again, or change something because of the platform?

Download Changes as CSV | Data Model of Dummy

Before You Upgrade

The data models of this step could not be compared, so changes of tables and columns that break a statement are not known. The data model of this driver comes from build 24.0.193-PROD+4785 in the 26.0 workspace and from build 25.0.205-PROD+5751 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.

No other change of this step is marked as breaking.

Top 5 Changes

Changes that can break a statement first, then by importance. Columns are summarised per table in the data model.

Data model

Do my statements and views still work? Tables, views, table functions, columns, parameters, keys, code values, packages and procedures that appear, disappear, are renamed or change type.

Not available. The data model of this driver comes from build 24.0.193-PROD+4785 in the 26.0 workspace and from build 25.0.205-PROD+5751 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.

Provider attributes

Do I have to change my connection string, provider file or settings? Attributes of the connection and settings of the driver that appear, disappear or change default or place where they can be set.

Not available. The data model of this driver comes from build 24.0.193-PROD+4785 in the 26.0 workspace and from build 25.0.205-PROD+5751 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.

Capabilities

What can the driver do with a table? Whether a table or table function can be selected from, inserted into, updated and deleted from.

Not available. The data model of this driver comes from build 24.0.193-PROD+4785 in the 26.0 workspace and from build 25.0.205-PROD+5751 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.

Performance

Is it faster, and does it call the platform less? Paging, batching, caching, filters and projections sent to the platform, fewer requests, less memory.

  • 1 changes
  • commits

Demonstration driver returns only the rows and columns that are asked for

The driver copies only the selected columns and honours a plain row limit without a filter, instead of handing all demo rows to the engine.

  • importance 1
  • confidence medium

Bug fixes

Is the defect that I met repaired? Wrong or missing rows, wrong values, crashes and wrong messages, repaired in a release line that had the defect.

  • 3 changes
  • commits

Commit after inserts on the demonstration driver no longer fails

A commit with collected insert actions on the demonstration driver ended in an error of the engine; the driver now accepts and ignores the collected actions.

  • importance 1
  • confidence low
Demonstration driver reports the log-on code of the user

The driver returned no user log-on code; it now returns the one of the shared base, as other drivers do.

  • importance 1
  • confidence medium
Selecting a partition in the demonstration driver marked the wrong partitions

Of the named demo partitions only the default one could be shown as selected when several partitions were selected, because the last three used the selection as their write permission. The selection and the defaults are now taken from the selected and default partitions.

  • importance 1
  • confidence medium

Enhancements

What can I do now that I could not? New functions and options that are not a table or a column.

  • 1 changes
  • commits

Demonstration driver can simulate many partitions and refused calls

Two new connection attributes let the demonstration driver generate more partitions, which can be read in parallel, and refuse every so many calls the way a platform does when it is asked too much. Without the attributes the driver behaves as before.

  • importance 1
  • confidence medium

Log-on and platform

Do I have to log on again, or change something because of the platform? Log-on and token handling, scopes and permissions, a new version of the platform API, retired endpoints and changed limits.

  • 0 changes
  • commits

No changes in this group.

More Information

How This Note Was Made

  • Commit message concerns ANSI/SQL Server drivers; the only Dummy change is an override of HandlePostponedInsertActions, whose base implementation throws itgengpr042. Whether a 26.0 session could reach that path was not traced.
  • Commit items were classified by one reader; the model changes are derived and need no reading.
  • Commits: the commits of the driver directory in the range that have no equivalent patch in the older state, without merges and version stamps; each was classified by reading its message and change.
  • Model: the NDJSON files of data-models/database of the workspace of each release are compared record by record; only fields that both models have are compared, and texts are counted, not listed.
  • A model generated from a later build of the same release (for example 26.0.340 for 26.0) stands for the release.
  • 7 links between a change and a source commit are recorded.
  • 1 exclusions are recorded in the audit of the note.