invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Tixly

Driver Release Note - Cloud

Tixly 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

Data models compared: 26.0.340-PROD+6295 and 27.0.6-PROD+6293.

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.

  • 24 changes
  • 19 can break a statement
  • 0 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
    • 18
    • 16 can break a statement
    • Do my statements and views still work?
  • Provider attributes
    • 2
    • Do I have to change my connection string, provider file or settings?
  • Capabilities
    • 2
    • 2 can break a statement
    • What can the driver do with a table?
  • Performance
    • 1
    • Is it faster, and does it call the platform less?
  • Bug fixes
    • 1
    • 1 can break a statement
    • Is the defect that I met repaired?
  • Enhancements
    • 0
    • 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

These changes can stop an existing statement, view, connection string or script from working:

Top 13 Changes

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

  1. Column DUMMY is removed from Tixly.Permission.Permission_ConfirmPermissionRegisterRemove
    • Data model
    • Breaks an existing statement or script.
  2. Column DUMMY is removed from Tixly.Permission.Permission_ConfirmRegisterPermission
    • Data model
    • Breaks an existing statement or script.
  3. Package tly_customers is removed
    • Data model
    • Breaks an existing statement or script.
  4. Package tly_permission is removed
    • Data model
    • Breaks an existing statement or script.
  5. Package tly_webuser is removed
    • Data model
    • Breaks an existing statement or script.
  6. Procedure tly_customers.customers_addcustomermetadata is removed
    • Data model
    • Breaks an existing statement or script.
  7. Procedure tly_customers.customers_addpremissionscustomer is removed
    • Data model
    • Breaks an existing statement or script.
  8. Procedure tly_customers.customers_addpremissionscustomers is removed
    • Data model
    • Breaks an existing statement or script.
  9. Tixly.Customer.Customers can no longer insert
    • Capabilities
    • Breaks an existing statement or script.
  10. Tixly.Customer.Customers can no longer update
    • Capabilities
    • Breaks an existing statement or script.
  11. Tixly is read only: write endpoints and their functions are no longer offered
    • Bug fixes
    • Breaks an existing statement or script.
  12. Attribute max-discovered-column-count is added
    • Provider attributes
    • Importance 3 of 5.
  13. Lower memory use when reading JSON answers
    • Performance
    • Importance 1 of 5.

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.

  • 18 changes
  • model files

Columns

0 added, 2 removed, 2 changed, in 3 tables.

Tixly.Native.NATIVEPLATFORMSCALARREQUESTS: 0 added, 0 removed, 2 changed

  • ~ DURATION_MS (database_data_type: int64 → double)
  • ~ DURATION_MS (dotnet_data_type: int64 → double)

Tixly.Permission.Permission_ConfirmPermissionRegisterRemove: 0 added, 1 removed, 0 changed

  • - DUMMY

Tixly.Permission.Permission_ConfirmRegisterPermission: 0 added, 1 removed, 0 changed

  • - DUMMY

Parameters, Packages and Procedures, Keys and Code Values

Package tly_customers is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Package tly_permission is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Package tly_webuser is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_customers.customers_addcustomermetadata is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_customers.customers_addpremissionscustomer is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_customers.customers_addpremissionscustomers is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_customers.customers_removecustomertag is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_customers.customers_removepremissionscustomer is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_customers.customers_tagcustomer is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_customers.customers_tagcustomers is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_permission.permission_registerdeletion is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_permission.permission_registerpermission is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_webuser.webuser_createcustomer is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4
Procedure tly_webuser.webuser_tagwebuser is removed

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • importance 4

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.

  • 2 changes
  • model files

Engine-wide connection attributes change

28 attributes added, 3 removed and 5 settings of attributes changed. These attributes belong to the SQL engine and exist for every driver; the Query Tool notes describe them.

  • importance 2
Attribute max-discovered-column-count is added

Can be set from connection string, SET statement, provider file, log-on. Default 250.

  • importance 3

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.

  • 2 changes
  • model files

Tixly.Customer.Customers can no longer insert

The driver no longer supports insert on Tixly.Customer.Customers. The driver is meant to be read only.

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • true → false
  • importance 4
Tixly.Customer.Customers can no longer update

The driver no longer supports update on Tixly.Customer.Customers. The driver is meant to be read only.

What to Do

Check statements, views and scripts that use it before the upgrade.

  • can break a statement
  • true → false
  • importance 4

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

Lower memory use when reading JSON answers

The driver reads the answers of Tixly with a lighter JSON reader that allocates less memory, and error answers are read with the shared default JSON settings.

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

  • 1 changes
  • commits

Tixly is read only: write endpoints and their functions are no longer offered

The driver no longer turns the POST, PUT, PATCH and DELETE operations of the Tixly specification into inserts, updates, deletes and package functions. Tixly is only meant to be read. The columns named DUMMY that served those operations are gone as well.

What to Do

Remove statements that insert into or update the Customers view and calls of the procedures of the packages tly_customers, tly_permission and tly_webuser; change Tixly data in Tixly itself.

  • can break a statement
  • importance 3
  • confidence medium

Enhancements

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

  • 0 changes
  • commits

No changes in this group.

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.

In Numbers

Objects of the data model at both ends of the step.

Objects 26.0 27.0 Change
tables 20 20 +0
views 1 1 +0
table functions 0 0 +0
columns 3,912 3,910 -2
function parameters 174 174 +0
attributes of driver 0 1 +1
tables that can insert 2 1 -1
tables that can update 1 0 -1
tables that can delete 0 0 +0

More Information

How This Note Was Made

  • 2026-11-01T12:05:52.1916246Z
  • 2026-11-01T11:55:19.2064558Z
  • Fields that only the newer model has.
  • Fields that only the newer model has.
  • Fields that only the newer model has.
  • Fields that only the newer model has.
  • Fields that only the newer model has.
  • Fields that only the newer model has.
  • Fields that only the newer model has.
  • 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.
  • 22 links between a change and a source commit are recorded.