> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/release-notes/october-2-2025.md).

# October 2, 2025

Release for 10/2/2025

This is a small update that includes several stability fixes.

* Updated default charsets and collation settings for databases, to be consistent throughout all Middle installations.
  * Previously, different installations had sometimes different charset and collation settings.
  * Fixing this is important down the line for storing things like emojis without errors.
* Updating collation settings for Middle resource data to be case-sensitive for Primary Keys and Foreign Keys. In this way, two keys with different cases will be correctly regarded as different.
  * This also fixes a crash that could occur when storing UUIDs as primary keys.
* Fixing indexing strategy for Set Variable steps, which can cause Middle installations to run slowly, or downtime.
* Fixing a 500 error that could result from editing a Scheduled Workflow.
* Fixing an unexpected Node Parameter Error that could result from using CSV file exports in Workflows.
* Fixing a 500 error that could occur when connecting certain Apps.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.middle.app/middle-docs/release-notes/october-2-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.