Release notes of LogiusCor
Driver Release Note
LogiusCor driver 27.0, from 26.0
| Build | Date | Description |
|---|---|---|
26.0.4 |
22-03-2026 | first build of release 26.0 |
27. |
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.
- 2 changes
- 1 can break a statement
- 3 groups not available
This Note
Groups
- Data model
- Provider attributes
- Capabilities
- Performance 0
- Bug fixes 0
- Enhancements 1
- Log-on and platform 1
More
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
- 0
- Is it faster, and does it call the platform less?
- Bug fixes
- 0
- Is the defect that I met repaired?
- Enhancements
- 1
- What can I do now that I could not?
- Log-on and platform
- 1
- 1 can break a statement
- Do I have to log on again, or change something because of the platform?
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 none in the 26.0 workspace and from build none 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.
These changes can stop an existing statement, view, connection string or script from working:
- Use the new Logius OIN register address and an API key
- Request an API key from Logius and enter it as the password of the connection.
Top 2 Changes
Changes that can break a statement first, then by importance. Columns are summarised per table in the data model.
- Use the new Logius OIN register address and an API key
- Log-on and platform
- Breaks an existing statement or script.
- Show the date the Logius COR driver was created and last reviewed
- Enhancements
- 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 none in the 26.0 workspace and from build none 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 none in the 26.0 workspace and from build none 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 none in the 26.0 workspace and from build none 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.
- 0 changes
- commits
No changes in this group.
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.
- 0 changes
- commits
No changes in this group.
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
Show the date the Logius COR driver was created and last reviewed
The registration of the driver holds the date it was created and the date it was last fully reviewed against the platform, both 27 December 2017.
- 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.
- 1 changes
- commits
Use the new Logius OIN register address and an API key
Logius moved the COR register to a new address behind an API gateway and made an API key mandatory. The driver now connects to the new address and asks for the API key as the password of the connection. Errors of the gateway and of the register are reported with clear messages, including the Logius reference.
What to Do
Request an API key from Logius and enter it as the password of the connection.
- can break a statement
- importance 5
- confidence medium
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.
- 2 links between a change and a source commit are recorded.