invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of In-Memory Storage

Driver Release Note - Internal

In-Memory Storage 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
    • 2
    • Is it faster, and does it call the platform less?
  • Bug fixes
    • 2
    • 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

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 22.1.262-BETA+4120 in the 26.0 workspace and from build 22.1.262-BETA+4120 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 22.1.262-BETA+4120 in the 26.0 workspace and from build 22.1.262-BETA+4120 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 22.1.262-BETA+4120 in the 26.0 workspace and from build 22.1.262-BETA+4120 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 22.1.262-BETA+4120 in the 26.0 workspace and from build 22.1.262-BETA+4120 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.

  • 2 changes
  • commits

CREATE TABLE in the in-memory driver uses less memory

Creating an in-memory table from a result set no longer builds a full second copy of the rows first. Rows are taken in batches into a table that other statements do not see yet, and the table replaces its predecessor only when it is complete. A create of a large table registers its inserts as bulk inserts.

  • importance 3
  • confidence medium
In-memory tables are safe for concurrent use and deletes, updates and inserts are faster

Every in-memory table now has its own read and write lock, so parallel branches of a statement can read and change a table without damaging it. A row is removed in constant time instead of rebuilding the indexes after each delete, so a volume delete is no longer quadratic in the size of the table. An update replaces the row as a whole, so a reader never sees a half-updated row, and new rows are added to the existing indexes instead of invalidating them.

  • importance 3
  • 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.

  • 2 changes
  • commits

CREATE TABLE in the in-memory driver reports success after creating the table

After a table was created the driver answered that it was not capable, which is the answer for a table that could not be created. It now answers that the call was successful.

  • importance 2
  • confidence medium
Rows and size of reads and writes of the in-memory driver are registered correctly

A create of an in-memory table registered only the size of its name and no rows, and a limited read registered the size of the whole table. The registrations now carry the rows and the estimated size that were really moved.

  • importance 2
  • 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

A statement on an in-memory table can be cancelled while rows are being read

Reading a large stored result from an in-memory table did not check for cancellation, so a cancelled statement kept running until all rows were cloned. The check now takes place for every row.

  • importance 2
  • confidence high

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 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.