invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Chargebee

Driver Release Note - Cloud

Chargebee 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
    • 2
    • Is the defect that I met repaired?
  • Enhancements
    • 1
    • What can I do now that I could not?
  • Log-on and platform
    • 1
    • Do I have to log on again, or change something because of the platform?

Download Changes as CSV | Data Model of Chargebee

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.1.3-BETA+4689 in the 26.0 workspace and from build 24.1.3-BETA+4689 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.

  1. Read Chargebee custom fields of type URL
    • Bug fixes
    • Importance 3 of 5.
  2. Read answers of the platform with less memory
    • Performance
    • Importance 2 of 5.
  3. Add measured throughput figures for time estimates
    • Enhancements
    • Importance 2 of 5.
  4. Mark the Chargebee site name as required at log-on
    • Log-on and platform
    • Importance 2 of 5.
  5. Avoid a failure on filters without a column when reading by key
    • Bug fixes
    • 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.

Not available. The data model of this driver comes from build 24.1.3-BETA+4689 in the 26.0 workspace and from build 24.1.3-BETA+4689 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.1.3-BETA+4689 in the 26.0 workspace and from build 24.1.3-BETA+4689 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.1.3-BETA+4689 in the 26.0 workspace and from build 24.1.3-BETA+4689 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

Read answers of the platform with less memory

The driver reads the JSON answers of the platform with a reader that allocates less memory. Large downloads put less load on memory and garbage collection.

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

Read Chargebee custom fields of type URL

A custom field of type URL used to stop the retrieval of the metadata with a validation error. It is now read as text. The creation date in the related messages is shown as a date instead of a number.

  • importance 3
  • confidence high
Avoid a failure on filters without a column when reading by key

A filter that does not point at a column no longer causes a failure when the driver checks for a filter on the key.

  • importance 1
  • confidence low

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

Add measured throughput figures for time estimates

The driver now carries figures per table on latency and rows per minute, derived from logged use. These figures feed estimates of how long a statement runs.

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

  • 1 changes
  • commits

Mark the Chargebee site name as required at log-on

The site name is a required field of the log-on, so that a connection without it is refused before a request is made.

  • importance 2
  • confidence medium

More Information

How This Note Was Made

  • Added sf.Field != null in two lookups of filters on the primary key. Which statement produced the failure was not established; marked by the commit as a nullability fix.
  • 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.
  • 9 links between a change and a source commit are recorded.